How severe is CVE-2022-26500?

CVE-2022-26500 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2022-26500?

Affected package information for CVE-2022-26500 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2022-26500?

Apply the veeam veeam backup \& replication security patch or hotfix for CVE-2022-26500 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2022-26500 across my infrastructure?

Inventory every veeam veeam backup \& replication deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2022-26500 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2022-26500?

O3 detects and blocks CVE-2022-26500 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2022-26500 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-26500, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-26500?

CVE-2022-26500 has an EPSS (Exploit Prediction Scoring System) score of 5.9%, placing it in the 92th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2022-26500 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2022-26500 (Veeam Backup & Replication Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-12-13. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-01-03. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2022-26500?

CVE-2022-26500 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2022-26500?

CVE-2022-26500 affects veeam veeam backup \& replication (4 versions, e.g. 9.5.0.1536, 9.5.4.2615, 10.0.1.4854…). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2022-26500 published, and has it been updated?

CVE-2022-26500 was published on March 17, 2022 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-12-13 — agencies required to remediate by 2023-01-03 · Ransomware

CVE-2022-26500

HIGH

Improper limitation of path names in Veeam Backup & Replication 9.5U3, 9.5U4,10.x, and 11.x allows remote authenticated users access to internal API functions that allows attackers…

Published

Mar 17, 2022

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

5.9%probability of exploitation in next 30 days

Lower Risk92th percentile-0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Improper limitation of path names in Veeam Backup & Replication 9.5U3, 9.5U4,10.x, and 11.x allows remote authenticated users access to internal API functions that allows attackers to upload and execute arbitrary code.

Affected Products

1 product · 10 configurations

Application

veeam backup \& replicationveeam

≥ 11.0.0.825 && < 11.0.1.1261

4 versions

9.5.0.15369.5.4.261510.0.1.485411.0.1.1261

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Improper limitation of path names in Veeam Backup & Replication 9.5U3, 9…

cisa.govCISADec 2022

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every veeam veeam backup \& replication deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the veeam veeam backup \& replication security patch or hotfix for CVE-2022-26500 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2022-26500 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2022-26500. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2022-26500 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2022-26500 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works