CVE-2025-6297: dpkg-deb: Fix cleanup for control member with restricted directories
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.47% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: dpkg (Debian:12) 1.21.23; dpkg (Debian:13) 1.22.21; dpkg (openSUSE:Leap 15.6) 1.19.0.4-150000.4.7.1.
Low priority for now. Upgrade to dpkg (Debian:12) 1.21.23; dpkg (Debian:13) 1.22.21; dpkg (openSUSE:Leap 15.6) 1.19.0.4-150000.4.7.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
It was discovered that dpkg-deb does not properly sanitize directory permissions when extracting a control member into a temporary directory, which is documented as being a safe operation even on untrusted data. This may result in leaving temporary files behind on cleanup. Given automated and repeated execution of dpkg-deb commands on adversarial .deb packages or with well compressible files, placed inside a directory with permissions not allowing removal by a non-root user, this can end up in a DoS scenario due to causing disk quota exhaustion or disk full conditions.
- Published
- Jul 1, 2025
- Updated
- Jul 8, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-400
Report tools
Action score
32
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| debian | dpkg | cpe:2.3:a:debian:dpkg |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (debian). Independent of NVD's CPE analysis and usually ahead of it.
Debian dpkg
- before ed6bbd445dd8800308c67236ba35d08004c98e82affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian dpkgbefore 1.22.21
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | dpkg | before 1.21.23 | 1.21.23 |
| Debian:13 | dpkg | before 1.22.21 | 1.22.21 |
| openSUSE:Leap 15.6 | dpkg | before 1.19.0.4-150000.4.7.1 | 1.19.0.4-150000.4.7.1 |
| openSUSE:Leap 15.6 | update-alternatives | before 1.19.0.4-150000.4.7.1 | 1.19.0.4-150000.4.7.1 |
| openSUSE:Tumbleweed | dpkg | before 1.22.21-1.1 | 1.22.21-1.1 |
| SUSE:Linux Enterprise Micro 5.3 | update-alternatives | before 1.19.0.4-150000.4.7.1 | 1.19.0.4-150000.4.7.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP6 | dpkg | before 1.19.0.4-150000.4.7.1 | 1.19.0.4-150000.4.7.1 |
| SUSE:Linux Micro 6.0 | update-alternatives | before 1.22.0-2.1 | 1.22.0-2.1 |
| SUSE:Linux Micro 6.1 | update-alternatives | before 1.22.0-slfo.1.1_2.1 | 1.22.0-slfo.1.1_2.1 |
Same product
debian: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-1664directory traversal for in-place extracts with untrusted v2 and v3 source packages with debian.tar40Plan
- CVE-2017-8283dpkg-source in dpkg 1.3.0 through 1.18.23 is able to use a non-GNU patch program and does not offer a protection mechanism for…40Plan
- CVE-2015-0860Off-by-one error in the extracthalf function in dpkg-deb/extract.c in the dpkg-deb component in Debian dpkg 1.16.x before 1.16.17 and…31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2014-8625Jan 20, 2015 · Multiple format string vulnerabilities in the parse_error_msg function in parsehelp.c in dpkg before 1.17.22 allow remote attackers to…28Monitor
- ← EarlierCVE-2015-0840Apr 13, 2015 · The dpkg-source command in Debian dpkg before 1.16.16 and 1.17.x before 1.17.25 allows remote attackers to bypass signature verification…18Monitor
- Later →CVE-2026-2219Mar 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…30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:dpkg | 1.21.23 · Debian:12 | Package registry (OSV) |
| opensuse:dpkg | 1.19.0.4-150000.4.7.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:update-alternatives | 1.19.0.4-150000.4.7.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:dpkg | 1.19.0.4-150000.4.7.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6 | Package registry (OSV) |
| suse:update-alternatives | 1.19.0.4-150000.4.7.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.