{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48768 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-48768 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-48768 is a medium-severity vulnerability in Apache NuttX RTOS, published on 1 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-48768 and fix it if it is affected.\n\nWhat it is: CVE-2025-48768 is a medium-severity vulnerability in Apache NuttX RTOS, published on 1 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-48768 in the wild and no public exploit code.\n\nAffected product: Apache NuttX RTOS. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-48768/ (Markdown: https://insights.sbomify.com/CVE-2025-48768/index.md)","id":"CVE-2025-48768","markdown":"https://insights.sbomify.com/CVE-2025-48768/index.md","name":"CVE-2025-48768","record":{"aliases":["GHSA-hxp8-h2pw-f72f"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"NuttX RTOS","requires_auth":"none","summary":"Attackers with write access to network-exposed filesystems can trigger a null pointer dereference or assert, causing a denial of service in NuttX RTOS.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"nuttx","vendor":"apache"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-763","name":"Release of Invalid Pointer or Reference"}],"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.\n\nThis issue affects Apache NuttX RTOS: from 10.0.0 before 12.10.0.\n\nUsers 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Apache NuttX RTOS: fs/inode: fs_inoderemove root inode removal","id":"CVE-2025-48768","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Apache NuttX RTOS: fs/vfs/fs_rename: use after free","id":"CVE-2025-48769"},"packages":[],"prev":{"headline":"Missing authorization in Lovable","id":"CVE-2025-48757"},"products":["Apache NuttX RTOS"],"published":"2026-01-01","related":[{"cvss_score":9.8,"headline":"Apache NuttX RTOS: tools/bdf-converter.: tools/bdf-converter: Fix loop termination condition.","id":"CVE-2025-47868","kev_date_added":null,"published":"2025-06-16"},{"cvss_score":9.8,"headline":"Apache NuttX RTOS: examples/xmlrpc: Fix calls buffers size.","id":"CVE-2025-47869","kev_date_added":null,"published":"2025-06-16"},{"cvss_score":9.8,"headline":"Apache NuttX RTOS: NuttX Bluetooth Stack HCI and UART DoS/RCE Vulnerabilities.","id":"CVE-2025-35003","kev_date_added":null,"published":"2025-05-26"},{"cvss_score":9.8,"headline":"malloc, realloc and memalign implementations are vulnerable to integer wrap-arounds","id":"CVE-2021-26461","kev_date_added":null,"published":"2021-06-21"},{"cvss_score":9.8,"headline":"Apache NuttX (incubating) Out of Bound Write from invalid fragmentation offset value specified in the IP header","id":"CVE-2020-17529","kev_date_added":null,"published":"2020-12-09"},{"cvss_score":9.8,"headline":"Null dereference in Apache NuttX (incubating)","id":"CVE-2020-1939","kev_date_added":null,"published":"2020-05-12"},{"cvss_score":9.1,"headline":"Apache NuttX (incubating) Out of Bound Write from invalid TCP Urgent length","id":"CVE-2020-17528","kev_date_added":null,"published":"2020-12-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-05","vendors":["Apache Software Foundation"]},"summary":"Attackers with write access to network-exposed filesystems can trigger a null pointer dereference or assert, causing a denial of service in NuttX RTOS.","url":"https://insights.sbomify.com/CVE-2025-48768/"}