# CVE-2026-24801: A Potential SPA-vulnerability in Ralim/IronOS

> A path traversal vulnerability in IronOS firmware allows attackers to read or modify files via the BLE stack, requiring a firmware update.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/S:N/AU:N/R:U/V:C/RE:M/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-mjw4-g269-g6rc

## What is CVE-2026-24801?

CVE-2026-24801 is a medium-severity path traversal vulnerability in Ralim IronOS, published on 27 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in Ralim IronOS (source/Core/BSP/Pinecilv2/bl_mcu_sdk/components/ble/ble_stack/common/tinycrypt/source modules). This vulnerability is associated with program files ecc_dsa.C.

This issue affects IronOS: before v2.23-rc3.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-24801 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24801 and fix it if it is affected.

What it is: CVE-2026-24801 is a medium-severity path traversal vulnerability in Ralim IronOS, published on 27 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24801 in the wild and no public exploit code.

Affected product: Ralim IronOS. 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-2026-24801/ (Markdown: https://insights.sbomify.com/CVE-2026-24801/index.md)
```

## Sources

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

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