Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-vx9q-rhv9-3jvg

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

CVSS 6.3 MediumEPSS 0.0056 · 47th percentile

Published by the GitHub Advisory Database at 12 Dec 2025, 22:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.airlift:aircompressor-v3Maven<3.43.4
io.airlift:aircompressorMaven<2.0.32.0.3
Identifiers
GHSA-vx9q-rhv9-3jvg · CVE-2025-67721
Weakness (CWE)
CWE-125 · CWE-201
Tags
Published
12 Dec 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Two Maven packages are affected: io.airlift:aircompressor-v3 before 3.4 and io.airlift:aircompressor before 2.0.3, in their Java Snappy and LZ4 decompressors. A remote attacker who supplies crafted compressed input can read leftover contents of a reused output buffer, which may expose sensitive data in applications that reuse buffers across calls. Upgrade aircompressor-v3 to 3.4 or aircompressor to 2.0.3; alternatively, stop reusing the decompression buffer or clear it before each decompression call.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.3 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0056, the 47th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.