# CVE-2026-3479: pkgutil.get_data() does not enforce documented restrictions

> Attackers could potentially read arbitrary files via path traversal in pkgutil.get_data(), though the vendor disputes this as a vulnerability.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2026
- **Updated:** 7 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-3479, ECHO-c84e-dea4-ec4c, GHSA-43rw-359f-4h89, MINI-7q7x-rxp3-2ppf, MINI-8cv8-pf76-4gj2, MINI-c8r3-rcw9-8mq2, MINI-fvg5-6r76-6g9x, MINI-j2cp-79jc-95mq, PSF-2026-13, ROOT-OS-DEBIAN-11-CVE-2026-3479, ROOT-OS-DEBIAN-12-CVE-2026-3479, ROOT-OS-DEBIAN-13-CVE-2026-3479, SUSE-SU-2026:1365-1, openSUSE-SU-2026:10520-1, openSUSE-SU-2026:10521-1, openSUSE-SU-2026:10552-1, openSUSE-SU-2026:10553-1, openSUSE-SU-2026:10554-1, openSUSE-SU-2026:10782-1

## What is CVE-2026-3479?

CVE-2026-3479 is a path traversal vulnerability in CPython, published on 18 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DISPUTED: The project has clarified that the documentation was incorrect, and that pkgutil.get_data() has the same security model as open(). The documentation has been updated to clarify this point. There is no vulnerability in the function if following the intended security model.

pkgutil.get_data() did not validate the resource argument as documented, allowing path traversals.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 2.7.18-150000.114.1 |
| `python-base` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 2.7.18-150000.114.1 |
| `python-moto` | openSUSE:Tumbleweed | All versions | 5.2.1-1.1 |
| `python310` | openSUSE:Tumbleweed | All versions | 3.10.20-4.1 |
| `python311` | openSUSE:Tumbleweed | All versions | 3.11.15-5.1 |
| `python312` | openSUSE:Tumbleweed | All versions | 3.12.13-5.1 |
| `python313` | openSUSE:Tumbleweed | All versions | 3.13.13-1.1 |
| `python314` | openSUSE:Tumbleweed | All versions | 3.14.4-1.1 |

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

Apply the vendor's patch.

## Is CVE-2026-3479 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3479 is a path traversal vulnerability in CPython, published on 18 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3479 in the wild and no public exploit code.

Affected product: CPython. 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-3479/ (Markdown: https://insights.sbomify.com/CVE-2026-3479/index.md)
```

## Sources

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

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