How severe is GHSA-33w6-hvmq-gh4x?

No CVSS score has been assigned to GHSA-33w6-hvmq-gh4x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-33w6-hvmq-gh4x?

GHSA-33w6-hvmq-gh4x affects the following packages: diffoscope (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-33w6-hvmq-gh4x?

Update diffoscope to 256 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-33w6-hvmq-gh4x is resolved across your whole dependency graph.

How do I detect GHSA-33w6-hvmq-gh4x in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for diffoscope. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-33w6-hvmq-gh4x if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-33w6-hvmq-gh4x?

O3 pinpoints whether GHSA-33w6-hvmq-gh4x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-33w6-hvmq-gh4x actively exploited in the wild?

No public exploit code has been indexed for GHSA-33w6-hvmq-gh4x yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-33w6-hvmq-gh4x?

GHSA-33w6-hvmq-gh4x is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-33w6-hvmq-gh4x published, and has it been updated?

GHSA-33w6-hvmq-gh4x was published on February 27, 2024 and was last updated on December 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-33w6-hvmq-gh4x

GHSA-33w6-hvmq-gh4x is a Path Traversal vulnerability in diffoscope. O3 Security confirms whether GHSA-33w6-hvmq-gh4x is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

diffoscope Path Traversal vulnerability

Also known asCVE-2024-25711PYSEC-2024-41

Published

Feb 27, 2024

Updated

Dec 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 5, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍diffoscope

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`diffoscope`	all versions	256

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for diffoscope. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update diffoscope to 256 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-33w6-hvmq-gh4x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-33w6-hvmq-gh4x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-33w6-hvmq-gh4x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-33w6-hvmq-gh4x in your dependencies?

O3 detects GHSA-33w6-hvmq-gh4x across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works