Single Ran
8 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Single Ran, a product in the networking infrastructure space. Use it to gauge the current risk picture and drill into individual advisories.
Single Ran CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 8 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 8 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High1
- Medium5
- Low2
Latest CVEs
The 8 most recently published vulnerabilities affecting Single Ran.
- CVE-2025-24335SOAP message input validation fault could in theory cause OAM service resource exhaustion2.0
- CVE-2025-24334The Nokia Single RAN baseband reveals its software version through the MNO internal RAN management network3.3
- CVE-2025-24333Administrative user shell input validation fault6.4
- CVE-2025-24332Authenticated admin user can connect baseband internally from one board to another without needing to re-authentication7.1
- CVE-2025-24331Nokia Single RAN baseband OAM service extensive capabilities6.4
- CVE-2025-24330OAM service path traversal issue caused by a crafted SOAP message PlanId field within the RAN management network6.4
- CVE-2025-24329OAM service path traversal issue caused by a crafted SOAP message archive field within the RAN management network6.4
- CVE-2025-24328OAM service stack overflow caused by crafted SOAP message within the MNO internal RAN management network4.2
Product grouping is registry-driven, with AI assist and human review. How it works