How severe is GHSA-vx9q-rhv9-3jvg?

No CVSS score has been assigned to GHSA-vx9q-rhv9-3jvg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vx9q-rhv9-3jvg?

GHSA-vx9q-rhv9-3jvg affects the following packages: io.airlift:aircompressor-v3 (Maven), io.airlift:aircompressor (Maven). Ecosystems affected: Maven.

How do I fix GHSA-vx9q-rhv9-3jvg?

Update io.airlift:aircompressor-v3 to 3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vx9q-rhv9-3jvg is resolved across your whole dependency graph.

How do I detect GHSA-vx9q-rhv9-3jvg in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.airlift:aircompressor-v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vx9q-rhv9-3jvg 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-vx9q-rhv9-3jvg?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vx9q-rhv9-3jvg can be triaged on real exposure rather than presence alone.

Is GHSA-vx9q-rhv9-3jvg actively exploited in the wild?

No public exploit code has been indexed for GHSA-vx9q-rhv9-3jvg 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 is the EPSS score for GHSA-vx9q-rhv9-3jvg?

GHSA-vx9q-rhv9-3jvg has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-vx9q-rhv9-3jvg?

GHSA-vx9q-rhv9-3jvg is classified as Out-of-bounds Read (CWE-125), CWE-201 (CWE-201). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vx9q-rhv9-3jvg published, and has it been updated?

GHSA-vx9q-rhv9-3jvg was published on December 12, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-vx9q-rhv9-3jvg — aircompressor-v3

Fix: airlift/aircompressor#309

GHSA-vx9q-rhv9-3jvg is a Out-of-bounds Read vulnerability in io.airlift:aircompressor-v3. A fix is available for io.airlift:aircompressor-v3 — see the affected versions and patch details below.

aircompressor Snappy and LZ4 Java-based decompressor implementation can leak information from reused output buffer

Also known asCVE-2025-67721

Published

Dec 12, 2025

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-vx9q-rhv9-3jvg.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

☕io.airlift:aircompressor-v3☕io.airlift:aircompressor

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

Description

Summary

Incorrect handling of malformed data in Java-based decompressor implementations for Snappy and LZ4 allows remote attackers to read previous buffer contents via crafted compressed input. In applications where the output buffer is reused without being cleared, this may lead to disclosure of sensitive data.

Details

With certain crafted compressed inputs, elements from the output buffer can end up in the uncompressed output. This is relevant for applications that reuse the same output buffer to uncompress multiple inputs. This can be the case of a web server that allocates a fix-sized buffer for performance purposes. This is similar to GHSA-cmp6-m4wj-q63q.

Impact

Applications using aircompressor as described above may leak sensitive information to external unauthorized attackers.

Mitigation

The vulnerability is fixed in release 3.4 and 2.0.3. However, it can be mitigated by either:

Avoiding reuse of the decompression buffer across calls
Clearing the decompression buffer before a call to decompress data

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.airlift:aircompressor-v3`	all versions	3.4`io.airlift:aircompressor-v3:3.4`
☕Maven	`io.airlift:aircompressor`	all versions	2.0.3`io.airlift:aircompressor:2.0.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.airlift:aircompressor-v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.airlift:aircompressor-v3 to 3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vx9q-rhv9-3jvg 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vx9q-rhv9-3jvg can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vx9q-rhv9-3jvg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Incorrect handling of malformed data in Java-based decompressor implementations for Snappy and LZ4 allows remote attackers to read previous buffer contents via crafted compressed input. In applications where the output buffer is reused without being cleared, this may lead to disclosure of sensitive data. ### Details With certain crafted compressed inputs, elements from the output buffer can end up in the uncompressed output. This is relevant for applications that reuse the same output buffer to uncompress multiple inputs. This can be the case of a web server that allocates a fix-s

O3 Security · Impact-Aware SCA

Is GHSA-vx9q-rhv9-3jvg in your dependencies?

O3 Security finds GHSA-vx9q-rhv9-3jvg across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works