CVE-2026-13201

HIGHPre-NVD 7.35.2
EchelonGraph scoreMEDIUM confidence

Score 5.2 from GitHub Security Advisory published 2026-06-24. a secondary CVSS source baseline 7.3; sources differ by 2.1.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A flaw was found in KubeVirt's safepath package used by virt-handler. The OpenAtNoFollow function uses O_PATH|O_NOFOLLOW to obtain a file descriptor to a path leaf, but downstream operations resolve the path via /proc/self/fd/N using link-following syscalls. When the leaf is a symlink, the kernel dereferences it, defeating the intended no-follow protection. An attacker with access to a virt-launcher pod can exploit this to redirect virt-handler's IPC socket connections, including the notify socket used for VM domain lifecycle events. By hijacking this socket, the attacker can inject arbitrary domain events into virt-handler, causing it to take incorrect lifecycle actions, corrupt VM state in the Kubernetes API, or crash — resulting in sustained denial of VM management services for all virtual machines on the affected node. Additionally, the same symlink following flaw allows virt-handler to apply file ownership or permission changes to unintended host paths.

CVSS v3
7.3
EG Score
5.2(medium)
EPSS
2.5%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
Patch available. Sources: redhat.
redhat

2492203 – (CVE-2026-13201) CVE-2026-13201 kubevirt: virt-handler-rhel9: kubevirt: safepath symlink following in virt-handler enables notify socket hijacking and node-level VM disruption

https://bugzilla.redhat.com/show_bug.cgi?id=2492203
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-13201

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 12:13 UTCEG score recompute
  3. 2026-07-06 12:13 UTCGHSA enrichment
  4. 2026-07-05 12:53 UTCEG score recompute
  5. 2026-07-05 12:53 UTCGHSA enrichment
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 13:43 UTCEG score recompute
  9. 2026-07-04 13:43 UTCGHSA enrichment
  10. 2026-07-03 14:34 UTCEG score recompute
  11. 2026-07-03 14:34 UTCGHSA enrichment
  12. 2026-07-02 15:24 UTCEG score recompute
  13. 2026-07-02 15:24 UTCGHSA enrichment
  14. 2026-07-01 16:13 UTCEG score recompute
  15. 2026-07-01 16:13 UTCGHSA enrichment
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-30 17:04 UTCEG score recompute
  18. 2026-06-30 17:03 UTCGHSA enrichment
  19. 2026-06-29 17:52 UTCEG score recompute
  20. 2026-06-29 17:51 UTCGHSA enrichment
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-28 18:41 UTCEG score recompute
  23. 2026-06-28 18:41 UTCGHSA enrichment
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 04:56 UTCEPSS rescore
Show 12 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-27 19:31 UTCEG score recompute
  3. 2026-06-27 19:31 UTCGHSA enrichment
  4. 2026-06-27 03:08 UTCEPSS rescore
  5. 2026-06-26 20:21 UTCEG score recompute
  6. 2026-06-26 20:21 UTCGHSA enrichment
  7. 2026-06-26 01:51 UTCNVD updateCVSS v3 → 7.3 · severity → HIGH
  8. 2026-06-25 21:12 UTCEG score recompute
  9. 2026-06-25 21:12 UTCGHSA enrichment
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-24 22:02 UTCEG score recompute
  12. 2026-06-24 22:02 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-13201?
CVE-2026-13201 is a high vulnerability published on June 24, 2026. A flaw was found in KubeVirt's safepath package used by virt-handler. The OpenAtNoFollow function uses OPATH|ONOFOLLOW to obtain a file descriptor to a path leaf, but downstream operations resolve the path via /proc/self/fd/N using link-following syscalls. When the leaf is a symlink, the kernel…
When was CVE-2026-13201 disclosed?
CVE-2026-13201 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13201 actively exploited?
CVE-2026-13201 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13201?
CVE-2026-13201 has a CVSS v3 base score of 7.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.2.
How do I remediate CVE-2026-13201?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13201, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-13201

Explore →

Is Your Infrastructure Affected by CVE-2026-13201?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.