Quick answers
- Is CVE-2026-34760 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34760 being exploited in the wild.
- How severe is CVE-2026-34760?
- Medium severity, with a CVSS score of 5.9, published 2 April 2026.
- Which products and versions are affected?
- vllm (PyPI) ECOSYSTEM:introduced=0.5.5,fixed=0.18.0.
- Is there a fix for CVE-2026-34760?
- Yes. vllm (PyPI): upgrade to 0.18.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34760 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-34760?
- Check whether you run vllm (PyPI) or Vllm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- vllm (PyPI): upgrade to 0.18.0 or later
pip install "vllm>=0.18.0"
Technical details
vLLM (versions 0.5.5 to 0.17.x) utilized the Librosa library for audio processing, which defaulted to using 'numpy.mean' for mono downmixing (to_mono). This deviates from the international standard ITU-R BS.775-4, which specifies a weighted downmixing algorithm. This discrepancy creates a 'semantic gap' where the audio processed by the AI model (via Librosa) does not match the audio heard by humans. An attacker could potentially exploit this inconsistency to provide audio that is interpreted differently by the model than by a human reviewer. The issue was addressed in version 0.18.0 by removing the Librosa dependency and replacing it with pyav for audio processing.
Affected products
- vllm-project vllm >= 0.5.5, < 0.18.0
Identifiers
- CVE-2026-34760
- GHSA-6c4r-fmh3-7rh8
- PYSEC-2026-2299
Timeline
- 2026-03-21: patched: Fix merged into main branch via PR 37058
- 2026-04-02: disclosed: CVE-2026-34760 published