diffoscope Path Traversal vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2024-25711: 0.99% estimated exploitation activity in the next 30 days; percentile 62.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

diffoscope before 256 allows directory traversal via an embedded filename in a GPG file. Contents of any file, such as ../.ssh/idrsa, may be disclosed to an attacker. This occurs because the value of the gpg --use-embedded-filenames option is trusted.

Published by the source

27 Feb 2024, 03:31 UTC

Last modified by the source

5 Dec 2024, 05:37 UTC

Source last checked

26 Oct 2026, 13:12 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-33w6-hvmq-gh4x

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-33w6-hvmq-gh4x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-25711

Advisory: diffoscope Path Traversal vulnerability
IDs: CVE-2024-25711, GHSA-33w6-hvmq-gh4x
Record: https://patchnext.com/advisories/cve-2024-25711 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: diffoscope 256. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI diffoscope: affected < 256; fixed in 256

## Suggested inspection (read-only)
- `python -m pip show diffoscope`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on diffoscope.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-33w6-hvmq-gh4x (OSV record GHSA-33w6-hvmq-gh4x lists affected ranges: PyPI diffoscope >=0 <256 (fixed))
- Verified: https://github.com/advisories/GHSA-33w6-hvmq-gh4x (GitHub-reviewed advisory GHSA-33w6-hvmq-gh4x lists affected ranges: PyPI diffoscope >=0 <256)

Commands are suggestions: review each one before running it.