CVE-2026-2219

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

It was discovered that dpkg-deb (a component of dpkg, the Debian package management system) does not properly validate the end of the data stream when uncompressing a zstd-compressed .deb archive, which may result in denial of service (infinite loop spinning the CPU).

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

March 7, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Jun 10, 2026
Patch available.
generic

Making sure you're not a bot!

https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=6610297a62c0780dd0e80b0e302ef64fdcc9d313
generic Patch Available

#1129722 - dpkg-deb: Persistent hang on malformed .deb archives (DoS) CVE-2026-2219 - Debian Bug report logs

https://bugs.debian.org/1129722

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibdpkg-perl (1.22.21ubuntu3.2) @ 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
dpkg1.21.221.21.23—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
dpkg1.22.211.22.22—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
dpkg1.22.21 ... 1.23.5 (8 versions)1.23.6—

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 6× in last 7d / 28× 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 197 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-2219?
CVE-2026-2219 is a high vulnerability published on March 7, 2026. It was discovered that dpkg-deb (a component of dpkg, the Debian package management system) does not properly validate the end of the data stream when uncompressing a zstd-compressed .deb archive, which may result in denial of service (infinite loop spinning the CPU).
When was CVE-2026-2219 disclosed?
CVE-2026-2219 was first published in the National Vulnerability Database on March 7, 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-2026-2219 actively exploited?
CVE-2026-2219 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 64.2% of all scored CVEs.
What is the CVSS score of CVE-2026-2219?
CVE-2026-2219 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-2219?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2219, 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-2026-2219

Explore →

Is Your Infrastructure Affected by CVE-2026-2219?

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

Start Free Scan →Browse All CVEs