# CVE-2025-25733: Missing authorization in n/a

> Physically proximate attackers can arbitrarily modify SPI flash regions in Kapsch TrafficCom Roadside Units due to incorrect access control, degrading device security.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 26 Aug 2025
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-mhw2-47hc-23pg

## What is CVE-2025-25733?

CVE-2025-25733 is a low-severity missing authorization vulnerability in n/a, published on 26 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect access control in the SPI Flash Chip of Kapsch TrafficCom RIS-9160 & RIS-9260 Roadside Units (RSUs) v3.2.0.829.23, v3.8.0.1119.42, and v4.6.0.1211.28 allows physically proximate attackers to arbitrarily modify SPI flash regions, leading to a degradation of the security posture of the device.

Weakness: CWE-1233 (Security-Sensitive Hardware Controls with Missing Lock Bit Protection)

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

It affects 2 products.


Products: Kapsch Ris-9160 Firmware, Kapsch Ris-9260 Firmware.

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

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

## Is CVE-2025-25733 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-25732](https://insights.sbomify.com/CVE-2025-25732/): Privilege escalation in n/a (medium 6.8)
- [CVE-2025-25734](https://insights.sbomify.com/CVE-2025-25734/): Auth bypass in n/a (medium 6.8)
- [CVE-2025-25736](https://insights.sbomify.com/CVE-2025-25736/): Auth bypass in n/a (medium 6.8)
- [CVE-2025-25737](https://insights.sbomify.com/CVE-2025-25737/): Weak cryptography in n/a (medium 6.8)
- [CVE-2025-25735](https://insights.sbomify.com/CVE-2025-25735/): Security feature bypass in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25733 is a low-severity missing authorization vulnerability in n/a, published on 26 Aug 2025. 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-2025-25733 in the wild and no public exploit code.

Affected product: n/a. 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-25733/ (Markdown: https://insights.sbomify.com/CVE-2025-25733/index.md)
```

## Sources

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

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