Skip to main content
VulnerabilityPublished Updated

CVE-2024-25711: diffoscope · Path Traversal

Source CVE Database V5

0

Not known to be exploited · CVSS 7.1 High : upgrade to 256 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 256
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade the Debian debian/diffoscope package to 256.

Affected software

ProductAffectedFixed in
Debiandebian/diffoscopepkg:deb/debian/diffoscopeOther threatsAffected
  • <256
Fixed in
  • 256

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade diffoscope to version 256 or later once available, as this will include fixes for the directory traversal vulnerability. If you cannot patch yet, restrict access to systems running diffoscope to trusted users only and enforce strict local access controls. Avoid processing untrusted or unauthenticated GPG files with diffoscope. Implement monitoring and auditing of diffoscope usage to detect anomalous file access patterns. Consider sandboxing diffoscope executions to limit filesystem exposure. Educate developers and security teams about the risks of trusting embedded filenames in GPG files. Review and rotate any potentially exposed cryptographic keys or credentials as a precaution. Incorporate this vulnerability into supply chain security assessments and incident response plans.

Description

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

References

Community reviews

Loading reviews…