Security readout for executives and security teams
Plain-English summary
CVE-2026-23949 affects the Python package jaraco.context. If vulnerable versions process a malicious tar archive, files may be written outside the intended folder. This can expose sensitive files or overwrite unintended paths depending on application context. The published fix is version 6.1.0.
Executive priority
Prioritize remediation where affected Python systems process external archives, especially in CI/CD, package ingestion, or user-upload workflows. Systems not using jaraco.context.tarball() or untrusted tar archives have lower immediate exposure.
Technical view
jaraco.context versions 5.2.0 through before 6.1.0 contain a Zip Slip path traversal in jaraco.context.tarball(). The strip_first_component filter can transform paths containing ../ into traversal paths. The advisory also notes nested tarball handling can preserve the issue across multi-level archives.
Likely exposure
Exposure is most likely in Python applications or tooling that use jaraco.context.tarball() on attacker-controlled or untrusted tar archives. Organizations should also inventory vendored copies, but the cited affected product is jaraco.context.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation depends on a vulnerable application processing a crafted tar archive through the affected function.
Researcher notes
The root issue is CWE-22 path traversal caused by unsafe path component stripping before extraction. The advisory specifically calls out paths that become ../ traversals and nested tarball cases. Public sources name a patch commit and fixed version, but no active exploitation evidence is provided.
Mitigation direction
- Upgrade jaraco.context to version 6.1.0 or later.
- Avoid processing untrusted tar archives with vulnerable versions.
- Inventory direct and vendored jaraco.context copies in applications and build tooling.
- Check upstream vendor guidance for downstream packages using vendored jaraco.context code.
Validation and detection
- Check SBOMs and dependency manifests for jaraco.context versions >=5.2.0 and <6.1.0.
- Search application code for jaraco.context.tarball() usage.
- Confirm deployed environments run jaraco.context 6.1.0 or later.
- Review archive-ingestion workflows for untrusted tar input.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-23949 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N3.94Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/jaraco/jaraco.context/security/advisories/GHSA-58pv-8j8x-9vj2CVE reference · x_refsource_CONFIRM
- https://github.com/jaraco/jaraco.context/commit/7b26a42b525735e4085d2e994e13802ea339d5f9CVE reference · x_refsource_MISC
- https://github.com/jaraco/jaraco.context/blob/main/jaraco/context/__init__.py#L74-L91CVE reference · x_refsource_MISC
- https://github.com/pypa/setuptools/blob/main/setuptools/_vendor/jaraco/context.py#L55-L76CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.