{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5317 exists.","fix":"No fix has been published for CVE-2026-5317 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5317 is a medium-severity memory corruption vulnerability in Nothings stb, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-5317 and fix it if it is affected.\n\nWhat it is: CVE-2026-5317 is a medium-severity memory corruption vulnerability in Nothings stb, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5317 exists.\n\nAffected product: Nothings stb. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-5317/ (Markdown: https://insights.sbomify.com/CVE-2026-5317/index.md)","id":"CVE-2026-5317","markdown":"https://insights.sbomify.com/CVE-2026-5317/index.md","name":"CVE-2026-5317","record":{"aliases":["DEBIAN-CVE-2026-5317","GHSA-8mhm-8wmq-8793","UBUNTU-CVE-2026-5317"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"C audio decoding library","requires_auth":"none","summary":"Remote attackers can trigger an out-of-bounds write in the stb_vorbis decoder, potentially leading to code execution or crashes.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"stb_vorbis.c","vendor":"nothings"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A security flaw has been discovered in Nothings stb up to 1.22. This affects the function start_decoder of the file stb_vorbis.c. The manipulation results in out-of-bounds write. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Nothings stb stb_vorbis.c start_decoder out-of-bounds write","id":"CVE-2026-5317","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"LibRaw JPEG DHT losslessjpeg.cpp initval out-of-bounds write","id":"CVE-2026-5318"},"packages":[],"prev":{"headline":"Nothings stb stb_vorbis.c setup_free allocation of resources","id":"CVE-2026-5316"},"products":["stb"],"published":"2026-04-02","related":[{"cvss_score":7.3,"headline":"Multi-byte write heap buffer overflow in start_decoder in stb_vorbis","id":"CVE-2023-45676","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":7.3,"headline":"Heap buffer out of bounds write in start_decoder in stb_vorbis","id":"CVE-2023-45677","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":7.3,"headline":"Attempt to free an uninitialized memory pointer in vorbis_deinit in stb_vorbis","id":"CVE-2023-45679","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":7.3,"headline":"Out of bounds heap buffer write in stb_vorbis","id":"CVE-2023-45681","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":6.5,"headline":"0 byte write heap buffer overflow in start_decoder in stb_vorbis","id":"CVE-2023-45675","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":6.5,"headline":"Off-by-one heap buffer write in start_decoder in stb_vorbis","id":"CVE-2023-45678","kev_date_added":null,"published":"2023-10-20"},{"cvss_score":5.3,"headline":"Nothings stb stb_vorbis.c setup_free allocation of resources","id":"CVE-2026-5316","kev_date_added":null,"published":"2026-04-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-02","vendors":["Nothings"]},"summary":"Remote attackers can trigger an out-of-bounds write in the stb_vorbis decoder, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2026-5317/"}