vciy

CVE-2025-52958

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.

Junos OS and Junos OS Evolved: When route validation is enabled, BGP connection establishment failure causes RPD crash

CVE-2025-529584 of 4 sources documented this
21

rank 21 = 0 + 13 + 0 + 8 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00209  ·  without this subject the record ranks 21

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.3, from the CNA  ·  without this subject the record ranks 8

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 21

How much of the world it touches

NVD CPE configurations

12 products in the CPE ranges  ·  without this subject the record ranks 13

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 21

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$6,380over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$6,380 = $4.99M incident cost x 0.6121449559255632 exposure x 0.00209 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00209EPSSNOT IN KEVas of 2026-09-20
Severity5.3 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-07-12, 371 days at 0.00, as of 2026-07-18. 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 Juniper Networks Junos OS? 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.

Reachreachable from an adjacent network · no privileges required · no user interaction · high attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-617 Reachable Assertionreceipt
Published consequencesCWE-617: Availability: DoS: Crash, Exit, or Restart[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in22.2R3-S6; 22.4R3-S6; 23.2R2-S3; 23.4R2-S4; 24.2R2; 22.2R3-S6-EVO; 22.4R3-S6-EVO; 23.2R2-S3-EVO; 23.4R2-S4-EVO; 24.2R2-EVOreceipt
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

CVSS, the CNA5.3 MEDIUMreceipt
Exploit probability0.00209 · top 89% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned byjuniperreceipt
Recorded changes18 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productJuniper Networks Junos OS; Juniper Networks Junos OS Evolvedreceipt
Published rangesjuniper junos < 22.2; juniper junos 22.2; juniper junos 22.4; juniper junos 23.2receipt
Show all 12 published ranges
juniper junos < 22.2
juniper junos 22.2
juniper junos 22.4
juniper junos 23.2
juniper junos 23.4
juniper junos 24.2
juniper junos os evolved < 22.2
juniper junos os evolved 22.2
juniper junos os evolved 22.4
juniper junos os evolved 23.2
juniper junos os evolved 23.4
juniper junos os evolved 24.2
Fixed in22.2R3-S6; 22.4R3-S6; 23.2R2-S3; 23.4R2-S4; 24.2R2; 22.2R3-S6-EVO; 22.4R3-S6-EVO; 23.2R2-S3-EVO; 23.4R2-S4-EVO; 24.2R2-EVOreceipt

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.

Attack path

Adjacent networkno credentials, no interactionJuniper Networks Junos OSCWE-617 weaknessAvailability lossA:Hexploits CWE-617data compromise

What it is stated by the CNA

A Reachable Assertion vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS).On all Junos OS and Junos OS Evolved devices, when route validation is enabled, a rare condition during BGP initial session establishment can lead to an rpd crash and restart. This occurs specifically when the connection request fails during error-handling scenario. Continued session establishment failures leads to a sustained DoS condition.  This issue affects Junos OS: * All versions before 22.2R3-S6, * from 22.4 before 22.4R3-S6, * from 23.2 before 23.2R2-S3, * from 2 receipt

Read the rest of the CNA's description

3.4 before 23.4R2-S4, * from 24.2 before 24.2R2; Junos OS Evolved: * All versions before 22.2R3-S6-EVO, * from 22.4 before 22.4R3-S6-EVO, * from 23.2 before 23.2R2-S3-EVO, * from 23.4 before 23.4R2-S4-EVO, * from 24.2 before 24.2R2-EVO.

NVD's analysis a second authority

weakness
CWE-617
affected versions
juniper junos < 22.2; juniper junos 22.2; juniper junos 22.4; and 9 more, listed in full below
also scored by
[email protected] 6 CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:A/V:X/RE:M/U:Green · [email protected]…

check it yourself supportportal.juniper.net receipt

Movement the material steps

12 Jul 20250.00016
15 Jun 20260.00211 · scoring model v2026.06.15
18 Jul 20260.00209
Show all 18 observations
12 Jul 20250.00016
17 Jul 20250.00019
30 Jul 20250.00022
12 Aug 20250.00025
22 Aug 20250.00021
17 Sep 20250.00022
10 Nov 20250.00033
5 Dec 20259e-05
19 Dec 20250.00011
4 Feb 20260.00012
14 Feb 20260.00011
16 Mar 20260.00012
27 Mar 20260.00016
6 Apr 20260.00018
27 Apr 20260.00017
7 May 20260.00057
15 Jun 20260.00211
18 Jul 20260.00209

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.00209Published2025-07-11Index as of2026-07-18

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

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

Siblings and hubs

Records related to this one

Its defect family

juniper networks junos os

Of the 5 records in this family, this is the only one holding a stated fix version: 22.2R3-S6; 22.4R3-S6; 23.2R2-S3; 23.4R2-S4; 24.2R2; 22.2R3-S.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

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

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.