vciy

CVE-2025-24335

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

SOAP message input validation fault could in theory cause OAM service resource exhaustion

CVE-2025-243353 of 4 sources documented this
unranked

No rank

rank@v1 withholds a number for this record

nothing this rule scores is held for this record, so there is no ordering to state. That is a fact about the sources, not a finding about the software.

Hindsight · the state

0.00462EPSSNOT IN KEVas of 2026-09-20
Severitynot scored
Harmnot stated
Exploitationnone in held sources
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-07-02, 405 days at 0.00, as of 2026-08-11. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running Nokia Single RAN? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

ReachNo CVSS vector in held sources, so no reach or impact can be stated.
Weakness classCWE-1287 Improper Validation of Specified Type of Inputreceipt
Published consequencesCWE-1287: Other: Varies by Context[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in24R1-SR 2.1 MP and laterreceipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

Exploit probability0.00462 · top 61% of all CVEsreceipt
Assigned byNokiareceipt
Recorded changes18 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productNokia Single RANreceipt
Fixed in24R1-SR 2.1 MP and laterreceipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Nokia Single RAN baseband software versions earlier than 24R1-SR 2.1 MP contain a SOAP message input validation flaw, which in theory could potentially be used for causing resource exhaustion in the Single RAN baseband OAM service. No practical exploit has been detected for this flaw. However, the issue has been corrected starting from release 24R1-SR 2.1 MP by adding sufficient input validation for received SOAP requests, effectively mitigating the reported issue. receipt

NVD's analysis a second authority

weakness
CWE-1287
also scored by
2 CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L

check it yourself nokia.com receipt

Movement the material steps

2 Jul 20250.00018
15 Jun 20260.0044 · scoring model v2026.06.15
11 Aug 20260.00462
Show all 18 observations
2 Jul 20250.00018
3 Jul 20250.00021
8 Jul 20250.00023
23 Jul 20250.00027
3 Aug 20250.00025
8 Sep 20250.00029
1 Nov 20250.00041
28 Nov 20250.0002
10 Dec 20250.00024
26 Jan 20260.00026
5 Feb 20260.00025
7 Mar 20260.00027
18 Mar 20260.0003
28 Mar 20260.00033
18 Apr 20260.00029
28 Apr 20260.00088
15 Jun 20260.0044
11 Aug 20260.00462

18 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00462Published2025-07-02Index as of2026-08-11

The record had been public for 1 year, 1 month when this index was last written.

Published 2025-07-02 receipt · Index as of 2026-08-11 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2025-24335.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.