Skip to content
Noroxi
CVE-2026-3479· NVD / CVE Program· CNA PSF

pkgutil.get_data() does not enforce documented restrictions

Noroxi assessment

Priority: Monitor (action score 0/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.24% (FIRST EPSS).
  • Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Python Software Foundation CPython 3.13.13, 3.14.4, 3.15.0a8; cbl2 python3 3.9.19-19 on CBL-Mariner 2.0 Release Notes.

Low priority for now. Upgrade to Python Software Foundation CPython 3.13.13, 3.14.4, 3.15.0a8; cbl2 python3 3.9.19-19 on CBL-Mariner 2.0 Release Notes 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

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.

CVSS 0.0 · v4.0—No exploit Fix available
Published
Mar 18, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · 0.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · PSF
0.0
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2026-3479

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

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

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (PSF). Independent of NVD's CPE analysis and usually ahead of it.

  • Python Software Foundation CPython

    • before 3.13.13affected · python
    • 3.14.0 and later · before 3.14.4affected · python
    • 3.15.0a1 and later · before 3.15.0a8affected · python

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12pypy3from 0—
Debian:12python3.11from 0—
Debian:13python3.13from 0—
Debian:14python3.14from 0—
openSUSE:Leap 15.6python310-documentationbefore 3.10.20-150400.4.107.13.10.20-150400.4.107.1
openSUSE:Leap 15.6python311-documentationbefore 3.11.15-150600.3.53.13.11.15-150600.3.53.1
openSUSE:Leap 15.6python312-documentationbefore 3.12.13-150600.3.53.13.12.13-150600.3.53.1
openSUSE:Leap 16.0python313before 3.13.13-160000.1.13.13.13-160000.1.1
openSUSE:Leap 16.0python313-corebefore 3.13.13-160000.1.13.13.13-160000.1.1
openSUSE:Leap 16.0python313-documentationbefore 3.13.13-160000.1.13.13.13-160000.1.1
openSUSE:Leap 16.0python313-nogilbefore 3.13.13-160000.1.13.13.13-160000.1.1
openSUSE:Leap 16.0python313-nogil-nogil-corebefore 3.13.13-160000.1.13.13.13-160000.1.1
openSUSE:Tumbleweedpython-motobefore 5.2.1-1.15.2.1-1.1
openSUSE:Tumbleweedpython310before 3.10.20-4.13.10.20-4.1
openSUSE:Tumbleweedpython311before 3.11.15-5.13.11.15-5.1
openSUSE:Tumbleweedpython312before 3.12.13-5.13.12.13-5.1
openSUSE:Tumbleweedpython313before 3.13.13-1.13.13.13-1.1
openSUSE:Tumbleweedpython314before 3.14.4-1.13.14.4-1.1
openSUSE:Tumbleweedpython315before 3.15.0~a8-1.13.15.0~a8-1.1
Red Hat:hummingbird:1python-unversioned-commandbefore 0:3.14.4-1.hum10:3.14.4-1.hum1
Red Hat:hummingbird:1python3before 0:3.14.4-1.hum10:3.14.4-1.hum1
Red Hat:hummingbird:1python3-debugbefore 0:3.14.4-1.hum10:3.14.4-1.hum1
Red Hat:hummingbird:1python3-develbefore 0:3.14.4-1.hum10:3.14.4-1.hum1
Red Hat:hummingbird:1python3-idlebefore 0:3.14.4-1.hum10:3.14.4-1.hum1

+96

Other highest-scoring records for the same primary product.

  • CVE-2025-4517Arbitrary writes via tarfile realpath overflow
    37Monitor
  • CVE-2026-19445Use-after-free of a server-side SSLContext when sni_callback switches contexts
    36Monitor
  • CVE-2026-6100Use-after-free in lzma.LZMADecompressor, bz2.BZ2Decompressor, and gzip.GzipFile after re-use under memory pressure
    36Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-1299Jan 23, 2026 · email BytesGenerator header injection due to unquoted newlines
    24Monitor
  • ← EarlierCVE-2026-2297Mar 4, 2026 · SourcelessFileLoader does not use io.open_code()
    22Monitor
  • Later →CVE-2026-1502Apr 10, 2026 · HTTP client proxy tunnel headers not validated for CR/LF
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Python Software Foundation CPython3.13.13Vendor (CNA)
Python Software Foundation CPython3.14.4Vendor (CNA)
Python Software Foundation CPython3.15.0a8Vendor (CNA)
cbl2 python3 3.9.19-19 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
opensuse:python3113.11.15-150600.3.53.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python311-core3.11.15-150600.3.53.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python311-documentation3.11.15-150600.3.53.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python3123.12.13-150600.3.53.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python312-core3.12.13-150600.3.53.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python312-documentation3.12.13-150600.3.53.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:python-unversioned-command0:3.14.4-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python30:3.14.4-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.110:3.11.15-4.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.11-debug0:3.11.15-4.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.11-devel0:3.11.15-4.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.11-idle0:3.11.15-4.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.11-libs0:3.11.15-4.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.120:3.12.13-3.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.12-debug0:3.12.13-3.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.12-devel0:3.12.13-3.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.12-idle0:3.12.13-3.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.12-libs0:3.12.13-3.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.12-test0:3.12.13-3.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.12-tkinter0:3.12.13-3.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.130:3.13.13-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.140:3.14.4-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
suse:python3103.10.20-150400.4.107.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:python310-core3.10.20-150400.4.107.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:python3113.11.15-150600.3.53.1 · SUSE:Linux Enterprise Module for Python 3 15 SP7Package registry (OSV)
suse:python311-core3.11.15-150600.3.53.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)

+4

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-4517288 days apartArbitrary writes via tarfile realpath overflow
    37Monitor
  • CVE-2026-1194097 days aparttarfile extraction filter bypass allows escaping the destination directory
    31Monitor
  • CVE-2025-4138288 days apartBypassing extraction filter to create symlinks to arbitrary targets outside extraction directory
    30Monitor
  • CVE-2025-4330288 days apartExtraction filter bypass for linking outside extraction directory
    30Monitor
  • CVE-2026-777478 days aparttarfile.data_filter path traversal bypass allows writing outside the extraction directory
    27Monitor
  • CVE-2026-19672154 days aparttarfile extraction filter bypass allows creation of directories outside the destination
    25Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Physical access to the device is required.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Physical
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

CVSS vector

CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records