Skip to main content
VulnerabilityPublished

CVE-2025-47869: Apache NuttX RTOS · Memory Buffer Overflow

Affects Apache NuttX RTOSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubapache/nuttx-appspkg:github/apache/nuttx-appsOther threatsAffected
  • =6.22
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should conduct a thorough audit of their Apache NuttX RTOS deployments to identify any use of the XMLRPC example application or custom code derived from it, especially in versions prior to 12.9.0. Specific mitigation steps include: 1) Upgrade to Apache NuttX RTOS version 12.9.0 or later, where the buffer size issue is corrected. 2) If immediate upgrade is not feasible, manually review and adjust buffer sizes in the device stats structure to at least CONFIG_XMLRPC_STRINGSIZE+1 to prevent overflow. 3) Implement strict input validation and bounds checking on all remotely received parameters within the XMLRPC interface. 4) Employ runtime protections such as stack canaries, address space layout randomization (ASLR), and memory protection units (MPUs) where supported by the hardware to mitigate exploitation impact. 5) Limit network exposure of devices running vulnerable code by enforcing network segmentation, firewall rules, and access controls to reduce attack surface. 6) Monitor device logs and network traffic for anomalous activity indicative of attempted exploitation. 7) Engage with device manufacturers or software vendors to confirm patch status and request updates if necessary. These targeted actions go beyond generic advice by focusing on the specific vulnerable component and operational context of Apache NuttX RTOS deployments.

Description

Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability was discovered in Apache NuttX RTOS apps/exapmles/xmlrpc application. In this example application device stats structure that stored remotely provided parameters had hardcoded buffer size which could lead to buffer overflow. Structure members buffers were updated to valid size of CONFIG_XMLRPC_STRINGSIZE+1. This issue affects Apache NuttX RTOS users that may have used or base their code on example application as presented in releases from 6.22 before 12.9.0. Users of XMLRPC in Apache NuttX RTOS are advised to review their code for this pattern and update buffer sizes as presented in the version of the example in release 12.9.0.

References

Community reviews

Loading reviews…