CVE-2025-14876

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-02-18. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in the virtio-crypto device of QEMU. A malicious guest operating system can exploit a missing length limit in the AKCIPHER path, leading to uncontrolled memory allocation. This can result in a denial of service (DoS) on the host system by causing the QEMU process to terminate unexpectedly.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

February 18, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
Patch available. Sources: redhat.
redhat

2423549 – (CVE-2025-14876) CVE-2025-14876 qemu-kvm: Unbounded allocation in virtio-crypto

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

CVE-2025-14876 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2025-14876

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuqemu-utils (1:10.1.0+ds-5ubuntu2.4) @ questing2026-06-12ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.0+ds-1 ... 1:9.2.2+ds-1~bpo12+1 (199 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.2+ds-2 ... 1:10.0.7+ds-0+deb13u1 (11 versions)1:10.0.8+ds-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
qemu1:10.0.2+ds-2 ... 1:10.2.0~rc1+ds-1 (30 versions)1:10.2.1+ds-1—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 27× 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 190 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-14876?
CVE-2025-14876 is a medium vulnerability published on February 18, 2026. A flaw was found in the virtio-crypto device of QEMU. A malicious guest operating system can exploit a missing length limit in the AKCIPHER path, leading to uncontrolled memory allocation. This can result in a denial of service (DoS) on the host system by causing the QEMU process to terminate…
When was CVE-2025-14876 disclosed?
CVE-2025-14876 was first published in the National Vulnerability Database on February 18, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-14876 actively exploited?
CVE-2025-14876 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.1% of all scored CVEs.
What is the CVSS score of CVE-2025-14876?
CVE-2025-14876 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-14876?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-14876, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-14876

Explore →

Is Your Infrastructure Affected by CVE-2025-14876?

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

Start Free Scan →Browse All CVEs