NXP MCUXpresso SDK rpmsg-lite TZM Example before 26.06.01-lts Secure Memory Disclosure via NSC Veneer Functions
- Exploited
- No known exploitation
- Fix
- Fixed in 26.12.00-pvw1, 26.06.01-lts
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 26.12.00-pvw1, 26.06.01-lts.
- Last modified
- 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? →
- 7/100 · provisional
- 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
Summary
The NXP MCUXpresso SDK rpmsg-lite TZM example is affected by a flaw in its non-secure-callable veneer functions that lets a non-secure caller pass unvalidated pointers and sizes, potentially exposing secure-world memory or causing a denial of service. An attacker with local access can reach it without logging in or any user action.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Improper input validation in non-secure-callable (NSC) veneer functions of the NXP MCUXpresso SDK rpmsg-lite multicore example (multicore_examples/rpmsg_lite_pingpong_tzm) up to releases 26.06.00-lts and 26.09.00 may allow a non-secure caller to supply unvalidated pointers and size values, potentially resulting in disclosure of secure-world memory to the non-secure domain, or denial of service. All software versions starting from 26.06.01-lts and 26.12.00-pvw1 have fixed this issue.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.8/10CVSS 6.8
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 26.12.00-pvw1, 26.06.01-lts.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- NXP MCUXpresso SDK
fixed in 26.12.00-pvw1; fixed in 26.06.01-lts
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-118786
Is CVE-2026-118786 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
Which versions are affected by CVE-2026-118786?
MCUXpresso SDK: before 26.12.00-pvw1; before 26.06.01-lts.Source: cve.now feed data
How do I fix CVE-2026-118786?
Upgrade to a fixed version: 26.12.00-pvw1, 26.06.01-lts.Source: cve.now feed data