OSV-2026-1018
Heap-buffer-overflow in decode_reason_code_and_cc
No score
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
What each source reports
OSV No score
Heap-buffer-overflow in decode_reason_code_and_cc
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
- Record
OSV-2026-1018- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
nsmdOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2026-1018 is a vulnerability with no CVSS score yet in nsmd, published July 5, 2026. No source lists public exploit code. No source names a fixed version.