# CVE-2025-67721: aircompressor — Fixed in 3.4

☕ Maven

Not in CISA KEV

# CVE-2025-67721 — aircompressor-v3

[Fix: airlift/aircompressor@f2b489b](https://github.com/airlift/aircompressor/commit/f2b489b398779b40c1ee29ddb11d7edef54ddc15)

CVE-2025-67721 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's Snappy and LZ4 Java-based decompressor implementation can leak information from reused output buffer

Also known as[GHSA-vx9q-rhv9-3jvg](/vulnerability/GHSA-vx9q-rhv9-3jvg)

Published

Dec 12, 2025

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 9, 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 CVE-2025-67721.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

0.00%0.34%0.68%1.03%0.1%0.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## 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](https://github.com/yawkat/lz4-java/security/advisories/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`

## Affected Products

1 product · 2 configurations

Application

`aircompressor`airlift

≥ 3.0 && < 3.4

range

## Detection & mitigation playbook

Open-source dependency

1.  ### 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.
    
2.  ### 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 CVE-2025-67721 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
    

## 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 CVE-2025-67721 in your dependencies?

Find it across Maven, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)