How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity low, availability low.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
- Attack vector: Network — reachable from anywhere that can route to the service.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: None — an unauthenticated stranger can try it.
- User interaction: Required — someone has to click, open or visit something.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
- Integrity impact: Low — limited, and the attacker does not choose what is affected.
- Availability impact: Low — limited, and the attacker does not choose what is affected.
Weakness class
CVE-2026-5317 is classified as CWE-119: Improper Restriction of Operations within Memory Buffer Bounds. A read or write is performed without confirming it stays inside the allocated buffer, corrupting adjacent memory.
Affected software
CVE-2026-5317 is recorded against 1 package.
- stb-vorbis.c (fixed in 1.22)
Timeline and source
Published on 2 April 2026 and last revised on 17 June 2026. A public exploit is known to exist, which raises the urgency of patching considerably. Record sourced from NVD.
References
gist.github.com
vuldb.com
vuldb.com
vuldb.com
Other advisories for this package
stb-vorbis.c has other advisories on record. If you are patching this one, these are worth checking on the same host:
Same weakness in other software
These advisories are the same class of weakness (CWE-119: Improper Restriction of Operations within Memory Buffer Bounds) in other software:
