CVE
Contiki-NG out-of-bounds access in MPL multicast seed-set handling
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Contiki-NG through 5.2 has an out-of-bounds access flaw in its MPL multicast code (mpl.c), where buffer_reclaim() and domain_set_free() read one element past the end of the seed_set array. A remote attacker who doesn't need to log in can flood MPL multicast messages to trigger out-of-bounds reads and writes of adjacent static memory, which can corrupt memory or crash the device.
Written by a model from the sources below. Verify against them.
Original description
Contiki-NG through 5.2 contains an out-of-bounds access vulnerability in buffer_reclaim() and domain_set_free() in mpl.c that iterate the seed_set array one element past its end. Remote attackers can flood MPL multicast messages to fill the buffered message set, triggering out-of-bounds reads and writes of adjacent static memory that cause memory corruption or a crash.
Who should check
Teams running Contiki-NG 5.2 or earlier with MPL multicast in use on their devices or networks
“Contiki-NG through 5.2 contains an out-of-bounds access vulnerability”
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Apply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130386 (Contiki-NG through 5.2 Out-of-Bounds Access in MPL Multicast Seed-Set Iteration), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130386 (entry last updated 2026-11-17):
Affected:
- Contiki-NG Contiki-NG: through 5.2
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Contiki-NG 5.2 or earlier (source: https://www.vulncheck.com/advisories/contiki-ng-through-5.2-out-of-bounds-access-in-mpl-multicast-seed-set-iteration)
- Attacker floods MPL multicast messages to fill the buffered message set (source: https://www.vulncheck.com/advisories/contiki-ng-through-5.2-out-of-bounds-access-in-mpl-multicast-seed-set-iteration)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130386 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130386 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/contiki-ng/contiki-ng/pull/3304
- https://github.com/contiki-ng/contiki-ng/blob/4ccd1a3b9e767f168d12ec3df187fe6b7dc736b5/os/net/ipv6/multicast/mpl.c#L490-L506
- https://www.vulncheck.com/advisories/contiki-ng-through-5.2-out-of-bounds-access-in-mpl-multicast-seed-set-iteration
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130386
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130386"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Contiki-NG Contiki-NG
through 5.2
Evidence 5
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130386
Is CVE-2026-130386 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
In Contiki-NG's MPL multicast code, iterating over the buffered seed set can read and write past the bounds of a static memory area. Remote attackers can trigger this by flooding MPL multicast messages to fill the buffered message set, which can corrupt memory or crash the device.Source: vulncheck.com
Which versions are affected by CVE-2026-130386?
Contiki-NG: through 5.2.Source: cve.now feed data
Am I affected, and how do I check?
Contiki-NG versions 5.2 and earlier are listed as affected, with no earlier lower bound given in the facts. The setup involves devices that use MPL multicast and can receive multicast traffic from the network. To check a build, run the version command in the Contiki-NG tree or look at the release tag it was built from.Source: vulncheck.com
How do I fix CVE-2026-130386?
No fixed version or vendor patch identifier is listed in the checked facts, so no upgrade target can be named from these sources. Check the Contiki-NG release notes and the advisory for a fix before relying on any specific version.Source: vulncheck.com