Skip to content
Fencer Intel
high 8.6

CVE-2026-23949 json

jaraco.context Has a Path Traversal Vulnerability

published 9mo ago modified last mo. also GHSA-58pv-8j8x-9vj2 , PYSEC-2026-1469 , EUVD-2026-3592

cvss
8.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

jaraco.context, an open-source software package that provides some useful decorators and context managers, has a Zip Slip path traversal vulnerability in the `jaraco.context.tarball()` function starting in version 5.2.0 and prior to version 6.1.0. The vulnerability may allow attackers to extract files outside the intended extraction directory when malicious tar archives are processed. The strip_first_component filter splits the path on the first `/` and extracts the second component, while allowing `../` sequences. Paths like `dummy_dir/../../etc/passwd` become `../../etc/passwd`. Note that this suffers from a nested tarball attack as well with multi-level tar files such as `dummy_dir/inner.tar.gz`, where the inner.tar.gz includes a traversal `dummy_dir/../../config/.env` that also gets translated to `../../config/.env`. Version 6.1.0 contains a patch for the issue.

Patch / fix

  • pypi jaraco-context 6.1.0
  • jaraco jaraco.context 6.1.0
  • setuptools Debian 14 84.0.0-2
  • jaraco.context Debian 13 6.0.1-1+deb13u1
  • jaraco.context Debian 14 6.0.1-2

debian advisories DEBIAN-CVE-2026-23949

  • jaraco.context Ubuntu 25.10 6.0.1-1ubuntu0.1

ubuntu advisories UBUNTU-CVE-2026-23949

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • python-jaraco.context SLES for SAP applications 16.0, SLES 16.0 5.3.0-160000.3.1

suse advisories SUSE-SU-2026:20139-1

  • python-jaraco.context openSUSE Leap 16.0 5.3.0-160000.3.1
  • python-jaraco.context openSUSE Tumbleweed 6.1.0-1.1

opensuse advisories openSUSE-SU-2026:20095-1openSUSE-SU-2026:10077-1

Is CVE-2026-23949 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-23949 updated cvss 8.6

jaraco.context: jaraco.context: Path traversal via malicious tar archives

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
9mo ago

Exploit prediction

0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/jaraco/jaraco.context/security/advisories/GHSA-58pv-8j8x-9vj2 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
OSV 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi jaraco-context
>=5.2.0, <6.1.0
6.1.0

Affected products

  • jaraco jaraco.context

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.