{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2022-26501 in the wild since at least 13 Dec 2022, including in ransomware campaigns.","fix":"No fix has been published for CVE-2022-26501 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 Jan 2023.","what":"CVE-2022-26501 is a critical missing authorization vulnerability in n/a, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-26501 and fix it if it is affected.\n\nWhat it is: CVE-2022-26501 is a critical missing authorization vulnerability in n/a, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2022-26501 in the wild since at least 13 Dec 2022, including in ransomware campaigns.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-26501/ (Markdown: https://insights.sbomify.com/CVE-2022-26501/index.md)","id":"CVE-2022-26501","markdown":"https://insights.sbomify.com/CVE-2022-26501/index.md","name":"CVE-2022-26501","record":{"aliases":["GHSA-vhpf-rh57-x3v9"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Backup and Replication","requires_auth":"none","summary":"Attackers can bypass authentication controls in Veeam Backup \u0026 Replication to access protected resources without credentials.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"veeam_backup_\\\u0026_replication","vendor":"veeam"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Veeam Backup \u0026 Replication 10.x and 11.x has Incorrect Access Control (issue 1 of 2).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"Veeam Backup \u0026 Replication Remote Code Execution","id":"CVE-2022-26501","indexable":true,"kev":{"dateAdded":"2022-12-13","dueDate":"2023-01-03","knownRansomwareCampaignUse":"Known","product":"Backup \u0026 Replication","requiredAction":"Apply updates per vendor instructions.","vendorProject":"Veeam","vulnerabilityName":"Veeam Backup \u0026 Replication Remote Code Execution Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2022-26502"},"packages":[],"prev":{"headline":"Veeam Backup \u0026 Replication Remote Code Execution","id":"CVE-2022-26500"},"products":["n/a"],"published":"2022-03-17","related":[{"cvss_score":9.8,"headline":"Veeam Backup and Replication Deserialization","id":"CVE-2024-40711","kev_date_added":"2024-10-17","published":"2024-09-07"},{"cvss_score":8.8,"headline":"Veeam Backup \u0026 Replication Remote Code Execution","id":"CVE-2022-26500","kev_date_added":"2022-12-13","published":"2022-03-17"},{"cvss_score":7.5,"headline":"Veeam Backup \u0026 Replication Cloud Connect Missing Authentication for Critical Function","id":"CVE-2023-27532","kev_date_added":"2023-08-22","published":"2023-03-10"},{"cvss_score":10,"headline":"Missing authorization in Backup and Replication","id":"CVE-2026-21666","kev_date_added":null,"published":"2026-03-12"},{"cvss_score":10,"headline":"Missing authorization in Backup and Replication","id":"CVE-2026-21667","kev_date_added":null,"published":"2026-03-12"},{"cvss_score":10,"headline":"Code injection in Backup and Replication","id":"CVE-2026-21669","kev_date_added":null,"published":"2026-03-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["n/a"]},"summary":"Attackers can bypass authentication controls in Veeam Backup \u0026 Replication to access protected resources without credentials.","url":"https://insights.sbomify.com/CVE-2022-26501/"}