vciy

CVE-2025-59960

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: DHCP Option 82 messages from clients being passed unmodified to the DHCP server

CVE-2025-599604 of 4 sources documented this
29

rank 29 = 0 + 19 + 0 + 10 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.00260  ·  without this subject the record ranks 29

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.4, from the CNA  ·  without this subject the record ranks 10

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 29

How much of the world it touches

NVD CPE configurations

19 products in the CPE ranges  ·  without this subject the record ranks 19

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$7,940over 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

$7,940 = $4.99M incident cost x 0.6121449559255632 exposure x 0.0026 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.0026EPSSNOT IN KEVas of 2026-09-20
Severity7.4 HIGHreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-01-16, 241 days at 0.00, as of 2026-09-14. arc-rules@v1

Foresight · where to check next

LinuxApple macOSpolkitPalo Alto59960

This record is one instance of CWE-754, improper check for unusual or exceptional conditions. The index holds 642 prior instances of this class, 5 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

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 · low attack complexityreceipt
ImpactComplete availability loss, with impact beyond the vulnerable componentreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-754 Improper Check for Unusual or Exceptional Conditionsreceipt
Published consequencesCWE-754: Integrity, Availability: DoS: Crash, Exit, or Restart, Unexpected State[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in21.2R3-S10; 21.4R3-S12; 22.4R3-S8; 23.2R2-S5; 23.4R2-S6; 24.2R2-S2; 24.4R2; 25.2R1-S1, 25.2R2; 21.4R3-S12-EVO; 22.4R3-S8-EVO; 23.2R2-S5-EVO; 23.4R2-S6-EVO…receipt
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 CNA7.4 HIGHreceipt
Exploit probability0.0026 · top 82% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned byjuniperreceipt
Recorded changes13 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productJuniper Networks Junos OS; Juniper Networks Junos OS Evolvedreceipt
Published rangesjuniper junos < 21.2; juniper junos 21.2; juniper junos 21.4; juniper junos 22.2receipt
Show all 19 published ranges
juniper junos < 21.2
juniper junos 21.2
juniper junos 21.4
juniper junos 22.2
juniper junos 22.4
juniper junos 23.2
juniper junos 23.4
juniper junos 24.2
juniper junos 24.4
juniper junos 25.2
juniper junos os evolved < 21.4
juniper junos os evolved 21.4
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
juniper junos os evolved 24.4
juniper junos os evolved 25.2
Fixed in21.2R3-S10; 21.4R3-S12; 22.4R3-S8; 23.2R2-S5; 23.4R2-S6; 24.2R2-S2; 24.4R2; 25.2R1-S1, 25.2R2; 21.4R3-S12-EVO; 22.4R3-S8-EVO; 23.2R2-S5-EVO; 23.4R2-S6-EVO…receipt

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-754 weaknessAdjacent componentsscope changeAvailability lossA:Hexploits CWE-754scope changedata compromise

What it is stated by the CNA

An Improper Check for Unusual or Exceptional Conditions vulnerability in the Juniper DHCP service (jdhcpd) of Juniper Networks Junos OS and Junos OS Evolved allows a DHCP client in one subnet to exhaust the address pools of other subnets, leading to a Denial of Service (DoS) on the downstream DHCP server. By default, the DHCP relay agent inserts its own Option 82 information when forwarding client requests, optionally replacing any Option 82 information provided by the client. When a specific DHCP DISCOVER is received in 'forward-only' mode with Option 82, the device should drop the message unless 'trust-option82' is configured. receipt

Read the rest of the CNA's description

Instead, the DHCP relay forwards these packets to the DHCP server unmodified, which uses up addresses in the DHCP server's address pool, ultimately leading to address pool exhaustion. This issue affects Junos OS:  * all versions before 21.2R3-S10, * from 21.4 before 21.4R3-S12, * all versions of 22.2, * from 22.4 before 22.4R3-S8,  * from 23.2 before 23.2R2-S5,  * from 23.4 before 23.4R2-S6,  * from 24.2 before 24.2R2-S2,  * from 24.4 before 24.4R2,  * from 25.2 before 25.2R1-S1, 25.2R2. Junos OS Evolved: * all versions before 21.4R3-S12-EVO,  * all versions of 22.2-EVO, * from 22.4 before 22.4R3-S8-EVO,  * from 23.2 before 23.2R2-S5-EVO,  * from 23.4 before 23.4R2-S6-EVO,  * from 24.2 before 24.2R2-S2-EVO,  * from 24.4 before 24.4R2-EVO,  * from 25.2 before 25.2R1-S1-EVO, 25.2R2-EVO.

NVD's analysis a second authority

weakness
CWE-754
affected versions
juniper junos < 21.2; juniper junos 21.2; juniper junos 21.4; and 16 more, listed in full below
also scored by
[email protected] 6.3 CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:N/SA:H/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:Y/R:U/V:C/RE:M/U:Amber · [email protected]…

check it yourself supportportal.juniper.net kb.juniper.net receipt

Movement the material steps

16 Jan 20260.0002
15 Jun 20260.0024 · scoring model v2026.06.15
14 Sep 20260.0026

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 13 observations
16 Jan 20260.0002
21 Jan 20260.00025
4 Feb 20260.00029
16 Feb 20260.00039
18 Feb 20260.00013
26 Feb 20269e-05
24 Mar 20260.0001
17 May 20260.00012
13 Jun 20269e-05
15 Jun 20260.0024
14 Aug 20260.00252
3 Sep 20260.00239
14 Sep 20260.0026

13 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.0026Published2026-01-15Index as of2026-09-14

Exploit probability more than doubled between 2026-06-13 and 2026-06-15 (0.00009 → 0.0024) and the record had been public for 7 months when this index was last written.

Published 2026-01-15 receipt · Index as of 2026-09-14 derived

The pattern, elsewhere

This record is one instance of CWE-754, improper check for unusual or exceptional conditions. The index holds 642 prior instances of this class, 5 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2025-39682 · Linuxmatches 4 of 9KEV listed · 2025receipt
CVE-2023-41992 · Apple macOSmatches 3 of 9KEV listed · 2023receipt
CVE-2023-41993 · Apple macOSmatches 3 of 9KEV listed · 2023receipt
CVE-2021-3560 · polkitmatches 3 of 9KEV listed · 2022receipt
CVE-2024-3393 · Palo Alto Networks Cloud NGFWonly 1 attribute comparableKEV listed · 2024receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

642 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

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

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.