CVE-2026-13208

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: 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 virt-handler domain notify server. The gRPC handlers for HandleDomainEvent and HandleK8SEvent derive the VMI identity (namespace/name) solely from the request body without validating it against the connection's origin. Each virt-launcher pod connects through a per-VMI pipe socket, but no identity tag is propagated from the pipe path to the server handlers. This allows a compromised virt-launcher process to send forged domain lifecycle events for any other VMI scheduled on the same node, causing virt-handler to erroneously update that VMI's state and disrupt its lifecycle management.

CVSS v3
6.5
EG Score
6.5(high)
EPSS
0.7%
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

2492220 – (CVE-2026-13208) CVE-2026-13208 kubevirt: virt-handler-rhel9: kubevirt: virt-handler notify server trusts VMI identity from unauthenticated gRPC request body

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

cve-details

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

Vendor Advisories for CVE-2026-13208(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 38× 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 20:36 UTCEG score recompute
  2. 2026-07-06 20:35 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-05 20:39 UTCEG score recompute
  5. 2026-07-05 20:39 UTCGHSA enrichment
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 20:47 UTCEG score recompute
  9. 2026-07-04 20:46 UTCGHSA enrichment
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-03 20:54 UTCEG score recompute
  12. 2026-07-03 20:54 UTCGHSA enrichment
  13. 2026-07-02 21:03 UTCEG score recompute
  14. 2026-07-02 21:02 UTCGHSA enrichment
  15. 2026-07-01 21:11 UTCEG score recompute
  16. 2026-07-01 21:10 UTCGHSA enrichment
  17. 2026-07-01 15:06 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-06-30 21:18 UTCEG score recompute
  20. 2026-06-30 21:18 UTCGHSA enrichment
  21. 2026-06-29 21:24 UTCEG score recompute
  22. 2026-06-29 21:24 UTCGHSA enrichment
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-28 21:32 UTCEG score recompute
  25. 2026-06-28 21:32 UTCGHSA enrichment
Show 13 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-27 21:40 UTCEG score recompute
  5. 2026-06-27 21:40 UTCGHSA enrichment
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-26 21:48 UTCEG score recompute
  8. 2026-06-26 21:48 UTCGHSA enrichment
  9. 2026-06-25 21:54 UTCEG score recompute
  10. 2026-06-25 21:54 UTCGHSA enrichment
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-24 22:02 UTCEG score recompute
  13. 2026-06-24 22:02 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-13208?
CVE-2026-13208 is a medium vulnerability published on June 24, 2026. A flaw was found in KubeVirt's virt-handler domain notify server. The gRPC handlers for HandleDomainEvent and HandleK8SEvent derive the VMI identity (namespace/name) solely from the request body without validating it against the connection's origin. Each virt-launcher pod connects through a per-VMI…
When was CVE-2026-13208 disclosed?
CVE-2026-13208 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-13208 actively exploited?
CVE-2026-13208 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13208?
CVE-2026-13208 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-13208?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13208, 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-13208

Explore →

Is Your Infrastructure Affected by CVE-2026-13208?

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

Start Free Scan →Browse All CVEs