PatchSiren cyber security CVE debrief
CVE-2026-34760 Vllm CVE debrief
CVE-2026-34760 describes an audio-processing integrity issue in environments using vLLM with Librosa: mono downmixing defaults to numpy.mean, while ITU-R BS.775-4 calls for weighted downmixing. That mismatch can make audio interpreted by AI systems differ from what humans hear, creating inconsistent model inputs. The issue is assigned CVSS 5.9 (Medium) and is patched in vLLM 0.18.0.
- Vendor
- Vllm
- Product
- Unknown
- CVSS
- MEDIUM 5.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-02
- Original CVE updated
- 2026-07-24
- Advisory published
- 2026-04-02
- Advisory updated
- 2026-07-24
Who should care
Teams running vLLM or other audio-to-model pipelines that rely on Librosa for preprocessing, especially where speech, music, moderation, transcription, or classification decisions depend on faithful audio representation.
Technical summary
The vulnerable range in the NVD record is vllm:vllm versions 0.5.5 through before 0.18.0. The problem is not code execution; it is a mismatch in mono downmix behavior. Librosa’s default to_mono behavior uses numpy.mean, while the referenced international standard expects weighted downmixing. In practice, this can produce input audio that is numerically different from the channel balance perceived by listeners, which can affect downstream AI outputs. NVD lists the weakness as CWE-20 (Improper Input Validation) and the CVSS vector is AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L.
Defensive priority
Medium
Recommended defensive actions
- Upgrade to vLLM 0.18.0 or later, which the advisory says contains the fix.
- Review any audio ingestion or preprocessing paths that use Librosa to ensure mono conversion matches your intended policy and standards.
- If exact perceptual fidelity matters, validate preprocessing against the expected downmix method rather than relying on defaults.
- Test model outputs after upgrading to confirm that audio normalization and channel-mixing changes do not alter downstream behavior in unexpected ways.
- Track any downstream systems that consume preprocessed audio from vLLM so they can be revalidated after the change.
Evidence notes
This debrief is based only on the supplied NVD record and linked official references. The NVD entry marks the vulnerability as analyzed, lists affected versions from 0.5.5 to before 0.18.0, and provides CVSS 3.1 vector AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L. Official references include the GitHub patch commit, issue-tracking pull request, v0.18.0 release notes, and the vendor advisory.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-34760 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-34760
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-34760 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-34760
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://github.com/vllm-project/vllm/commit/c7f98b4d0a63b32ed939e2b6dfaa8a626e9b46c4
[email protected] - Patch
-
Source reference
Unverified legacy reference
URL: https://github.com/vllm-project/vllm/pull/37058
[email protected] - Issue Tracking
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://github.com/vllm-project/vllm/releases/tag/v0.18.0
[email protected] - Release Notes
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://github.com/vllm-project/vllm/security/advisories/GHSA-6c4r-fmh3-7rh8
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.