Canonical python-apt deb822 File TagSection.keys null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Canonical python-apt. This affects the function TagSection.keys of the component deb822 File Handler. Performing a manipulation results in null pointer dereference.
This vulnerability is known as CVE-2025-6966. Attacking locally is a requirement. No exploit is available.
Details
A vulnerability classified as problematic has been found in Canonical python-apt (the affected version is unknown). This affects the function TagSection.keys of the component deb822 File Handler. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. The summary by CVE is:
NULL pointer dereference in TagSection.keys() in python-apt on APT-based Linux systems allows a local attacker to cause a denial of service (process crash) via a crafted deb822 file with a malformed non-UTF-8 key.
The weakness was published by Julian Andres Klode. The advisory is shared at bugs.launchpad.net. This vulnerability is uniquely identified as CVE-2025-6966 since 07/01/2025. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 278731 (Debian dla-4408 : python-apt-common - security update), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Tenable (278731) and EUVD (EUVD-2025-201407). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 278731
Nessus Name: Debian dla-4408 : python-apt-common - security update
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/01/2025 CVE reserved12/05/2025 Advisory disclosed
12/05/2025 VulDB entry created
01/08/2026 VulDB entry last update
Sources
Advisory: bugs.launchpad.netResearcher: Julian Andres Klode
Status: Confirmed
CVE: CVE-2025-6966 (🔒)
GCVE (CVE): GCVE-0-2025-6966
GCVE (VulDB): GCVE-100-334485
EUVD: 🔒
Entry
Created: 12/05/2025 15:40Updated: 01/08/2026 06:12
Changes: 12/05/2025 15:40 (67), 12/08/2025 15:19 (1), 12/08/2025 15:32 (1), 12/16/2025 09:17 (2), 01/08/2026 06:12 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.