CVE-2022-26501
CRITICALCVSS 9.8/10Actively ExploitedEPSS 4.28%
Last modified
CVE-2022-26501 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. Veeam Backup & Replication 10.x and 11.x has Incorrect Access Control (issue 1 of 2).. CISA has confirmed active exploitation in the wild. EPSS estimates a 4.28% chance of exploitation in the next 30 days.
Description
Veeam Backup & Replication 10.x and 11.x has Incorrect Access Control (issue 1 of 2).
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploitation Status
This vulnerability is listed in CISA’s Known Exploited Vulnerabilities catalog, confirming active exploitation in the wild. Federal agencies must remediate by .
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Veeam | Veeam Backup \& Replication | >= 10.0.0.4442, < 10.0.1.4854 |
| Veeam | Veeam Backup \& Replication | >= 11.0.0.825, < 11.0.1.1261 |
| Veeam | Veeam Backup \& Replication | 10.0.1.4854 |
| Veeam | Veeam Backup \& Replication | 11.0.1.1261 |
References
- https://veeam.comVendor Advisory
- https://www.veeam.com/kb4288Vendor Advisory
- https://veeam.comVendor Advisory
- https://www.veeam.com/kb4288Vendor Advisory
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-26501US Government Resource
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2022-26501?
Veeam Backup & Replication 10.x and 11.x has Incorrect Access Control (issue 1 of 2).
How severe is CVE-2022-26501?
CVE-2022-26501 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 4.28% probability of exploitation in the next 30 days. This vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog.
How do I fix CVE-2022-26501?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2022-26501?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
