# CVE-2026-2219: Denial of service in dpkg

> Attackers can cause a denial of service via infinite loop in dpkg-deb when processing malicious zstd-compressed archives.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** AZL-79509, DEBIAN-CVE-2026-2219, ECHO-d2d4-4737-f820, GHSA-x8w5-j8fh-hpvp, MGASA-2026-0144, SUSE-SU-2026:20766-1, SUSE-SU-2026:20795-1, SUSE-SU-2026:22046-1, SUSE-SU-2026:22085-1, UBUNTU-CVE-2026-2219, USN-8249-1, openSUSE-SU-2026:10675-1, openSUSE-SU-2026:20909-1

## What is CVE-2026-2219?

CVE-2026-2219 is a high-severity denial of service vulnerability in Debian dpkg, published on 7 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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).

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2026-2219?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dpkg` | SUSE:Linux Enterprise Server 16.0 | All versions | 1.22.21-160000.3.1 |
| `update-alternatives` | SUSE:Linux Enterprise Server 16.0 | All versions | 1.22.21-160000.3.1 |
| `dpkg` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 1.22.21-160000.3.1 |
| `update-alternatives` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 1.22.21-160000.3.1 |
| `update-alternatives` | SUSE:Linux Micro 6.0 | All versions | 1.22.0-3.1 |
| `update-alternatives` | SUSE:Linux Micro 6.1 | All versions | 1.22.0-slfo.1.1_3.1 |
| `update-alternatives` | SUSE:Linux Micro 6.2 | All versions | 1.22.21-160000.3.1 |
| `dpkg` | openSUSE:Leap 16.0 | All versions | 1.22.21-160000.3.1 |
| `update-alternatives` | openSUSE:Leap 16.0 | All versions | 1.22.21-160000.3.1 |
| `dpkg` | openSUSE:Tumbleweed | All versions | 1.22.22-1.1 |

Products: Debian Dpkg.

## How do I fix CVE-2026-2219?

Apply the vendor's patch.

## Is CVE-2026-2219 being exploited?

There is no known exploitation of CVE-2026-2219 in the wild and no public exploit code.

## Other vulnerabilities in Debian dpkg

- [CVE-2017-8283](https://insights.sbomify.com/CVE-2017-8283/): Path traversal in n/a (critical 9.8)
- [CVE-2025-6297](https://insights.sbomify.com/CVE-2025-6297/): dpkg-deb: Fix cleanup for control member with restricted directories (high 8.2)
- [CVE-2004-2768](https://insights.sbomify.com/CVE-2004-2768/): Privilege escalation in n/a (high 7.2)
- [CVE-2014-3127](https://insights.sbomify.com/CVE-2014-3127/): Path traversal in n/a (high 7.1)
- [CVE-2014-8625](https://insights.sbomify.com/CVE-2014-8625/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2219 and fix it if it is affected.

What it is: CVE-2026-2219 is a high-severity denial of service vulnerability in Debian dpkg, published on 7 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2219 in the wild and no public exploit code.

Affected product: Debian dpkg. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2219/ (Markdown: https://insights.sbomify.com/CVE-2026-2219/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2219
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2219
- OSV: https://osv.dev/vulnerability/CVE-2026-2219

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2219/
Summaries are generated and may contain mistakes; the official description above is the record.