CVE-2026-13325

✕ Withdrawn — historical dataHIGHPre-NVD 8.5
8.5CVSS
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.5Exploit: None knownExposed services: Not assessed

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

A flaw was found in KubeVirt's migration proxy. When spec.configuration.migrations.disableTLS is set to true on the KubeVirt custom resource, the target virt-handler binds a plain TCP listener on all interfaces (0.0.0.0/::) on a random port with no authentication, peer allow-list, or handshake token. This listener proxies directly into the target virt-launcher's virtqemud control socket. An attacker with a running pod on the cluster network can connect to this listener and issue unfiltered libvirt RPC commands against another tenant's virtual machine, including reading VM memory and configuration, modifying VM state via QMP, or destroying the VM. The bind address is unconditionally 0.0.0.0 — configuring a dedicated migration network via migrations.network only changes the advertised migration IP, not the listener bind address, so the port remains reachable on the pod network even when a dedicated migration network is configured. The API documentation describes disableTLS as removing "the additional layer of live migration encryption" without disclosing that it also removes all mutual authentication.

CVSS v3
8.5
EchelonGraph score
Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

Published

June 26, 2026

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
No fix on record yet. Sources: redhat.
redhat

2493378 – (CVE-2026-13325) CVE-2026-13325 virt-handler-rhel9: kubevirt: kubevirt: DisableTLS migration setting removes authentication, exposing unauthenticated virtqemud proxy on all interfaces

https://bugzilla.redhat.com/show_bug.cgi?id=2493378
redhatMentions a patch (unverified)

cve-details

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

Vendor Advisories for CVE-2026-13325(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 0× in last 7d / 6× 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.

Showing the most recent 100 of 130 total refreshes for this CVE.

  1. 2026-09-23 08:19 UTCVendor advisory
  2. 2026-09-23 08:19 UTCGHSA enrichment
  3. 2026-09-18 07:16 UTCVendor advisory
  4. 2026-09-18 07:16 UTCGHSA enrichment
  5. 2026-09-12 15:40 UTCVendor advisory
  6. 2026-09-12 15:40 UTCGHSA enrichment
  7. 2026-08-31 00:52 UTCGHSA enrichment
  8. 2026-08-27 23:14 UTCGHSA enrichment
  9. 2026-08-23 08:36 UTCGHSA enrichment
  10. 2026-08-20 06:59 UTCGHSA enrichment
  11. 2026-08-16 21:48 UTCGHSA enrichment
  12. 2026-08-13 20:10 UTCGHSA enrichment
  13. 2026-08-10 18:33 UTCGHSA enrichment
  14. 2026-08-07 16:38 UTCGHSA enrichment
  15. 2026-08-04 15:09 UTCEPSS rescore
  16. 2026-08-04 15:01 UTCEG score recompute▼ 8.50
  17. 2026-08-04 15:01 UTCGHSA enrichment
  18. 2026-08-04 10:38 UTCEPSS rescore
  19. 2026-08-04 02:00 UTCGHSA enrichment
  20. 2026-08-03 14:05 UTCEG score recompute
  21. 2026-08-03 14:05 UTCGHSA enrichment
  22. 2026-08-03 10:35 UTCEPSS rescore
  23. 2026-08-03 02:07 UTCGHSA enrichment
  24. 2026-08-02 14:12 UTCEG score recompute
  25. 2026-08-02 14:12 UTCGHSA enrichment
Show 75 more
  1. 2026-08-02 02:26 UTCEPSS rescore
  2. 2026-08-02 02:17 UTCGHSA enrichment
  3. 2026-08-01 14:22 UTCEG score recompute
  4. 2026-08-01 14:22 UTCGHSA enrichment
  5. 2026-08-01 04:15 UTCEPSS rescore
  6. 2026-08-01 02:26 UTCGHSA enrichment
  7. 2026-07-31 14:27 UTCGHSA enrichment
  8. 2026-07-31 02:26 UTCEG score recompute
  9. 2026-07-31 02:26 UTCGHSA enrichment
  10. 2026-07-30 16:27 UTCEPSS rescore
  11. 2026-07-30 13:42 UTCEG score recompute
  12. 2026-07-30 13:42 UTCGHSA enrichment
  13. 2026-07-30 01:30 UTCEPSS rescore
  14. 2026-07-30 00:32 UTCGHSA enrichment
  15. 2026-07-29 08:51 UTCGHSA enrichment
  16. 2026-07-28 20:52 UTCEG score recompute
  17. 2026-07-28 20:52 UTCGHSA enrichment
  18. 2026-07-28 15:36 UTCEPSS rescore
  19. 2026-07-28 05:21 UTCGHSA enrichment
  20. 2026-07-27 17:10 UTCEG score recompute
  21. 2026-07-27 17:10 UTCGHSA enrichment
  22. 2026-07-27 14:13 UTCEPSS rescore
  23. 2026-07-27 02:37 UTCEG score recompute
  24. 2026-07-27 02:37 UTCGHSA enrichment
  25. 2026-07-26 14:54 UTCEPSS rescore
  26. 2026-07-26 14:54 UTCEPSS rescore
  27. 2026-07-26 14:41 UTCEG score recompute
  28. 2026-07-26 14:41 UTCGHSA enrichment
  29. 2026-07-25 14:17 UTCEPSS rescore
  30. 2026-07-24 14:17 UTCEPSS rescore
  31. 2026-07-23 14:18 UTCEPSS rescore
  32. 2026-07-23 03:05 UTCEG score recompute
  33. 2026-07-22 14:08 UTCEPSS rescore
  34. 2026-07-21 15:24 UTCEPSS rescore
  35. 2026-07-20 17:08 UTCEPSS rescore
  36. 2026-07-19 14:30 UTCEPSS rescore
  37. 2026-07-19 02:28 UTCEPSS rescore
  38. 2026-07-18 10:04 UTCEPSS rescore
  39. 2026-07-16 21:40 UTCGHSA enrichment
  40. 2026-07-16 17:02 UTCEPSS rescore
  41. 2026-07-16 09:45 UTCGHSA enrichment
  42. 2026-07-15 21:48 UTCGHSA enrichment
  43. 2026-07-15 16:57 UTCEPSS rescore
  44. 2026-07-15 09:40 UTCGHSA enrichment
  45. 2026-07-15 02:00 UTCEPSS rescore
  46. 2026-07-14 21:33 UTCGHSA enrichment
  47. 2026-07-14 09:38 UTCGHSA enrichment
  48. 2026-07-13 22:30 UTCEPSS rescore
  49. 2026-07-13 21:27 UTCGHSA enrichment
  50. 2026-07-13 09:30 UTCGHSA enrichment
  51. 2026-07-13 06:12 UTCEPSS rescore
  52. 2026-07-12 21:33 UTCGHSA enrichment
  53. 2026-07-12 09:38 UTCGHSA enrichment
  54. 2026-07-12 05:46 UTCEPSS rescore
  55. 2026-07-11 21:42 UTCGHSA enrichment
  56. 2026-07-11 09:47 UTCGHSA enrichment
  57. 2026-07-11 08:27 UTCEPSS rescore
  58. 2026-07-10 21:52 UTCGHSA enrichment
  59. 2026-07-10 09:57 UTCGHSA enrichment
  60. 2026-07-09 22:00 UTCGHSA enrichment
  61. 2026-07-09 19:10 UTCEPSS rescore
  62. 2026-07-09 10:05 UTCGHSA enrichment
  63. 2026-07-08 22:10 UTCGHSA enrichment
  64. 2026-07-08 15:15 UTCEPSS rescore
  65. 2026-07-08 15:15 UTCEPSS rescore
  66. 2026-07-08 10:14 UTCGHSA enrichment
  67. 2026-07-07 22:18 UTCGHSA enrichment
  68. 2026-07-07 13:46 UTCEPSS rescore
  69. 2026-07-07 10:23 UTCGHSA enrichment
  70. 2026-07-06 22:24 UTCGHSA enrichment
  71. 2026-07-06 16:27 UTCEPSS rescore
  72. 2026-07-06 10:29 UTCGHSA enrichment
  73. 2026-07-06 02:23 UTCEPSS rescore
  74. 2026-07-05 22:32 UTCGHSA enrichment
  75. 2026-07-05 10:36 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-13325?
CVE-2026-13325 is a high vulnerability published on June 26, 2026. A flaw was found in KubeVirt's migration proxy. When spec.configuration.migrations.disableTLS is set to true on the KubeVirt custom resource, the target virt-handler binds a plain TCP listener on all interfaces (0.0.0.0/::) on a random port with no authentication, peer allow-list, or handshake…
When was CVE-2026-13325 disclosed?
CVE-2026-13325 was first published on June 26, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13325 actively exploited?
CVE-2026-13325 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-13325?
CVE-2026-13325 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-13325?
No fix for CVE-2026-13325 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-13325 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-13325?

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

Book a Demo →Browse All CVEs