# CVE-2025-47869: Apache NuttX RTOS: examples/xmlrpc: Fix calls buffers size.

> A buffer overflow in the NuttX RTOS XMLRPC example allows attackers to cause memory corruption, potentially leading to code execution or denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2025
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-pqw8-wfp5-mgqq

## What is CVE-2025-47869?

CVE-2025-47869 is a critical memory corruption vulnerability in Apache NuttX RTOS, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-47869?

It affects 1 product.


Products: Apache Nuttx.

## How do I fix CVE-2025-47869?

No fix has been published for CVE-2025-47869 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-47869 being exploited?

There is no known exploitation of CVE-2025-47869 in the wild and no public exploit code.

## Other vulnerabilities in Apache NuttX RTOS

- [CVE-2025-47868](https://insights.sbomify.com/CVE-2025-47868/): Apache NuttX RTOS: tools/bdf-converter.: tools/bdf-converter: Fix loop termination condition. (critical 9.8)
- [CVE-2025-35003](https://insights.sbomify.com/CVE-2025-35003/): Apache NuttX RTOS: NuttX Bluetooth Stack HCI and UART DoS/RCE Vulnerabilities. (critical 9.8)
- [CVE-2021-26461](https://insights.sbomify.com/CVE-2021-26461/): malloc, realloc and memalign implementations are vulnerable to integer wrap-arounds (critical 9.8)
- [CVE-2020-17529](https://insights.sbomify.com/CVE-2020-17529/): Apache NuttX (incubating) Out of Bound Write from invalid fragmentation offset value specified in the IP header (critical 9.8)
- [CVE-2020-1939](https://insights.sbomify.com/CVE-2020-1939/): Null dereference in Apache NuttX (incubating) (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47869 and fix it if it is affected.

What it is: CVE-2025-47869 is a critical memory corruption vulnerability in Apache NuttX RTOS, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-47869 in the wild and no public exploit code.

Affected product: Apache NuttX RTOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-47869/ (Markdown: https://insights.sbomify.com/CVE-2025-47869/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-47869
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-47869
- OSV: https://osv.dev/vulnerability/CVE-2025-47869

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-47869/
Summaries are generated and may contain mistakes; the official description above is the record.