ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-3479

DISPUTED: The project has clarified that the documentation was incorrect, and that pkgutil.get_data() has the same security model as open().

Published Mar 18, 2026 · catalog updated Jun 17, 2026 · DISPUTED: The project has

Check if you run it

No confirmed exploitation is on record for CVE-2026-3479. EPSS is 0.25%. Act only if a listed version of DISPUTED: The project has is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (DISPUTED: The project has).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
None0.0
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.25%
Remediation
Advisory link
Affected products
See sources for product scope

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.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2026-3479

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-3479. EPSS is 0.25%. Act only if a listed version of DISPUTED: The project has is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-22: Path Traversal. EPSS 0.25%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 18, 2026 · NIST NVD

    Detected

    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.

  2. Jun 17, 2026 · NIST NVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2026-3479

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-3479

    30-day exploitation probability 0.3%

    first.org
  • NIST NVDVulnerability recordCVE-2026-3479

    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 mode

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.