CVE-2022-26503
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDeserialization of untrusted data in Veeam Agent for Windows 2.0, 2.1, 2.2, 3.0.2, 4.x, and 5.x allows local users to run arbitrary code with local system privileges.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVeeam Agent for Windows versions 2.0 through 5.x improperly handles deserialization of untrusted data, enabling a local authenticated user to execute arbitrary code with SYSTEM-level privileges by exploiting the insecure deserialization vulnerability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.0.0, < 4.0.2.2208>= 5.0.0, < 5.0.3.4708= 2.0= 2.1= 2.2= 3.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate Veeam Agent for Windows installationOpen Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID} or check C:\Program Files\Veeam\ for the Veeam Agent directory. Alternatively, run 'Get-WmiObject Win32_Product | Where-Object {$_.Name -like "Veeam*"}' in PowerShell.Affected if Veeam Agent for Windows is installed on the system
-
Identify installed Veeam Agent versionIn the registry uninstall key or via PowerShell (Get-WmiObject), locate the Version string (e.g., "5.0.0.1234"). Note the full version number including build.Affected if The displayed version falls within 2.0, 2.1, 2.2, 3.0.2, or between 4.0.0 and 4.0.2.2208, or between 5.0.0 and 5.0.3.4708
-
Confirm service presenceOpen Services.msc and look for 'Veeam Agent' or run 'Get-Service Veeam*' in PowerShell to verify the Veeam service is installed and running.Affected if The Veeam Agent service exists on the system, indicating the vulnerable component is present
-
Verify local authentication requirementReview system users and，确认本地账户存在 (run 'net user' or check Local Users and Groups). The vulnerability requires a local authenticated user account.Affected if Local user accounts exist on the machine, providing the attack vector for privilege escalation
A system is affected if Veeam Agent for Windows is installed with a version matching 2.0, 2.1, 2.2, 3.0.2, 4.0.0-4.0.2.2208, or 5.0.0-5.0.3.4708, and local user authentication is possible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data4.0.2.22085.0.3.4708
Apply the vendor-supplied patch or upgrade to a fixed version of Veeam Agent for Windows. Prioritize patching endpoints with local user access to reduce the privilege escalation attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26503 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-26503 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data