VulnerabilityPublished 1 Jan 2026Updated 5 Jan 2026

CVE-2025-48768: Apache NuttX RTOS · Release of Invalid Pointer or Reference

Affects Apache NuttX RTOSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 12.10.0 : update Apache NuttX RTOS when convenient.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 12.10.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubapache/nuttx`pkg:github/apache/nuttx`Other threats	Affected =10.0.0	Fixed in–

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

AI-suggested

To mitigate CVE-2025-48768, European organizations should: 1) Identify all devices and embedded systems running Apache NuttX RTOS versions between 10.0.0 and 12.10.0, especially those exposing filesystem write services over the network (e.g., FTP). 2) Upgrade affected devices to Apache NuttX RTOS version 12.10.0 or later, where the vulnerability is fixed. 3) If immediate upgrade is not feasible, restrict network access to vulnerable services using network segmentation, firewalls, or access control lists to limit exposure to trusted networks only. 4) Disable or restrict write access to filesystem services exposed externally unless absolutely necessary. 5) Monitor network traffic and device logs for unusual activity or signs of attempted exploitation, such as unexpected crashes or service interruptions. 6) Implement intrusion detection systems tailored to detect anomalous behavior on embedded devices. 7) Coordinate with device vendors or integrators to ensure timely patch deployment and security updates. 8) Review and harden device configurations to minimize attack surface, including disabling unused services and enforcing strong authentication where possible.

Description

Release of Invalid Pointer or Reference vulnerability was discovered in fs/inode/fs_inoderemove code of the Apache NuttX RTOS that allowed root filesystem inode removal leading to a debug assert trigger (that is disabled by default), NULL pointer dereference (handled differently depending on the target architecture), or in general, a Denial of Service. This issue affects Apache NuttX RTOS: from 10.0.0 before 12.10.0. Users of filesystem based services with write access that were exposed over the network (i.e. FTP) are affected and recommended to upgrade to version 12.10.0 that fixes the issue.

Impact

For European organizations, the primary impact of CVE-2025-48768 is the potential for denial of service on devices running Apache NuttX RTOS with network-exposed filesystem write services. This can disrupt critical embedded systems or IoT devices used in industrial control, telecommunications, or infrastructure monitoring. The denial of service could lead to operational downtime, loss of availability of essential services, and potential cascading effects in environments relying on continuous device operation. Since the vulnerability does not affect confidentiality or integrity, data breaches or unauthorized data modifications are unlikely. However, the disruption of service could impact sectors such as manufacturing, energy, transportation, and healthcare, where embedded systems are prevalent. The ease of remote exploitation without authentication increases the risk profile, especially for devices exposed to untrusted networks. Organizations relying on NuttX-based devices should assess their exposure and prioritize patching to maintain operational continuity.

CWE-763Release of Invalid Pointer or Reference (opens in a new tab)
Base weakness
The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.
Implementation
Only call matching memory management functions. Do not mix and match routines. For example, when you allocate a buffer with malloc(), dispose of the original pointer with free().
Implementation
When programming in C++, consider using smart pointers provided by the boost library to help correctly and consistently manage memory.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jan 2026, 18:58 UTC

WeaknessesCWE-763

Technical details

References

Community reviews

Related threats