OSV-2026-1018 Heap-buffer-overflow in decode_reason_code_and_cc
Not scored
Published
Check this codebase for OSV-2026-1018 and fix it if it is affected.
What it is: OSV-2026-1018 is a memory corruption vulnerability in nsmd, published on 5 Jul 2026.
Exploitation: There is no known exploitation of OSV-2026-1018 in the wild and no public exploit code.
Affected packages and fixed versions:
- nsmd (OSS-Fuzz): affected all versions; no fix listed
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/OSV-2026-1018/ (Markdown: https://insights.sbomify.com/OSV-2026-1018/index.md)
A heap buffer overflow in the NSM token response decoder can cause a crash, requiring a patch to prevent denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2026-1018?
OSV-2026-1018 is a memory corruption vulnerability in nsmd, published on 5 Jul 2026.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=530730549
Crash type: Heap-buffer-overflow READ 1
Crash state:
decode_reason_code_and_cc
decode_nsm_provide_token_resp
decode_nsm_provide_token_resp_fuzzer.cc
Which versions are affected by OSV-2026-1018?
1 open source package ship an affected version, including nsmd.
| Package | Affected | Fixed in |
|---|---|---|
nsmd OSS-Fuzz | All versions | None |
How do I fix OSV-2026-1018?
No fix has been published for OSV-2026-1018 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is OSV-2026-1018 being exploited?
There is no known exploitation of OSV-2026-1018 in the wild and no public exploit code.