CVE-2026-21909 | Junos OS and Junos OS Evolved: Receipt of specific IS-IS update packet causes memory leak leading to RPD crash

A Missing Release of Memory after Effective Lifetime vulnerability in the routing protocol daemon (rpd) Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated attacker controlling an adjacent IS-IS neighbor to send a specific update packet causing a memory leak. Continued receipt and processing of these packets will exhaust all available memory, crashing rpd and creating a Denial of Service (DoS) condition. Memory usage can be monitored through the use of the 'show task memory detail' command. For example: user@junos> show task memory detail | match ted-infra   TED-INFRA-COOKIE           25   1072     28   1184     229 user@junos> show task memory detail | match ted-infra   TED-INFRA-COOKIE           31   1360     34   1472     307 This issue affects: Junos OS:  * from 23.2 before 23.2R2,  * from 23.4 before 23.4R1-S2, 23.4R2,  * from 24.1 before 24.1R2;  Junos OS Evolved:  * from 23.2 before 23.2R2-EVO,  * from 23.4 before 23.4R1-S2-EVO, 23.4R2-EVO,  * from 24.1 before 24.1R2-EVO. This issue does not affect Junos OS versions before 23.2R1 or Junos OS Evolved versions before 23.2R1-EVO.

Published: 2026-01-15 Last update: 2026-01-23 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-21909 is rated Low Risk (29.4/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-21909

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-16 — 0.02% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-21909

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.1 4.0 HIGH
CVSS:4.0/AV:A/AC:L/AT:N/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:Y/R:A/V:C/RE:M/U:Green Click to expand
Attack vector (AV:A)
Attacker has to be on an adjacent/local network segment.
Attack complexity (AC:L)
Exploitation conditions are straightforward and stable.
Attack requirements (AT:N)
No additional preconditions are required beyond normal reachability.
Privileges required (PR:N)
No privileges are required.
User interaction (UI:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:N)
No confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:N)
No integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:H)
High availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N)
No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N)
No integrity impact on subsequent systems.
Subsequent system availability impact (SA:L)
Limited availability impact on subsequent systems.
Exploit maturity (threat) (E:X)
Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X)
Not evaluated.
Automatable (supplemental) (AU:Y)
Yes: all four kill-chain steps (reconnaissance, weaponization, delivery, exploitation) can be automated.
Recovery (supplemental) (R:A)
Automatic: services recover on their own after an attack.
Value density (supplemental) (V:C)
Concentrated: a single exploit event controls rich resources (e.g., a central server).
Vulnerability response effort (supplemental) (RE:M)
Moderate effort (remote update, disable subsystem, simple upgrade with minor service impact).
Provider urgency (supplemental) (U:GREEN)
Green: provider rates reduced urgency.
 — — [email protected]
6.5 3.1 MEDIUM
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 3.6 [email protected]

Weakness enumeration for CVE-2026-21909

Affected software / configurations for CVE-2026-21909

Vendor Product Version Raw CPE
juniper junos 23.2 cpe:2.3:o:juniper:junos:23.2:-:*:*:*:*:*:*
juniper junos 23.2 cpe:2.3:o:juniper:junos:23.2:r1:*:*:*:*:*:*
juniper junos 23.2 cpe:2.3:o:juniper:junos:23.2:r1-s1:*:*:*:*:*:*
juniper junos 23.2 cpe:2.3:o:juniper:junos:23.2:r1-s2:*:*:*:*:*:*
juniper junos 23.4 cpe:2.3:o:juniper:junos:23.4:-:*:*:*:*:*:*
juniper junos 23.4 cpe:2.3:o:juniper:junos:23.4:r1:*:*:*:*:*:*
juniper junos 23.4 cpe:2.3:o:juniper:junos:23.4:r1-s1:*:*:*:*:*:*
juniper junos 23.4 cpe:2.3:o:juniper:junos:23.4:r2:*:*:*:*:*:*
juniper junos 24.1 cpe:2.3:o:juniper:junos:24.1:-:*:*:*:*:*:*
juniper junos 24.1 cpe:2.3:o:juniper:junos:24.1:r1:*:*:*:*:*:*
juniper junos_os_evolved 23.2 cpe:2.3:o:juniper:junos_os_evolved:23.2:-:*:*:*:*:*:*
juniper junos_os_evolved 23.2 cpe:2.3:o:juniper:junos_os_evolved:23.2:r1:*:*:*:*:*:*
juniper junos_os_evolved 23.2 cpe:2.3:o:juniper:junos_os_evolved:23.2:r1-s1:*:*:*:*:*:*
juniper junos_os_evolved 23.2 cpe:2.3:o:juniper:junos_os_evolved:23.2:r1-s2:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:-:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:r1:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:r1-s1:*:*:*:*:*:*
juniper junos_os_evolved 23.4 cpe:2.3:o:juniper:junos_os_evolved:23.4:r2:*:*:*:*:*:*
juniper junos_os_evolved 24.1 cpe:2.3:o:juniper:junos_os_evolved:24.1:-:*:*:*:*:*:*
juniper junos_os_evolved 24.1 cpe:2.3:o:juniper:junos_os_evolved:24.1:r1:*:*:*:*:*:*

References for CVE-2026-21909

cvelogic Threat Intelligence