LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-21909 can let a neighboring IS-IS routing device crash Juniper’s routing process by repeatedly sending a specific update. The impact is denial of service, not data theft or code execution. Risk is highest for networks where untrusted or compromised devices can form IS-IS adjacencies with affected Junos routers.

Executive priority

High priority for routing environments using IS-IS on affected Juniper releases. The business risk is network instability or outage if a trusted-adjacent device is compromised or unauthorized. Patch during the next urgent network maintenance window, prioritizing core and aggregation routers.

Technical view

A CWE-401 memory leak in rpd affects Junos OS and Junos OS Evolved 23.2, 23.4, and 24.1 before specified fixed releases. An unauthenticated attacker controlling an adjacent IS-IS neighbor can trigger memory exhaustion through specific update packets, causing rpd to crash. CVSS v4.0 score is 7.1, availability impact high.

Likely exposure

Exposure requires an adjacent IS-IS neighbor. Internet-wide exposure is unlikely unless IS-IS adjacency is reachable from untrusted networks. Organizations using affected Junos versions with IS-IS enabled should treat compromised or unauthorized routing peers as the main risk.

Exploitation context

The sources do not report active exploitation, and the CVE is not marked KEV. Exploitation requires adjacency in the IS-IS routing domain and continued receipt of crafted updates to exhaust memory. This is a service availability risk for routing infrastructure.

Researcher notes

The advisory identifies the vulnerable component, affected release trains, fixed releases, trigger condition, and memory monitoring indicator. It does not provide public exploit code or report exploitation. Avoid assuming remote Internet exploitation; the attack vector is adjacent IS-IS neighbor access.

Mitigation direction

  • Upgrade Junos OS to 23.2R2, 23.4R1-S2, 23.4R2, 24.1R2, or later fixed releases.
  • Upgrade Junos OS Evolved to 23.2R2-EVO, 23.4R1-S2-EVO, 23.4R2-EVO, 24.1R2-EVO, or later.
  • Review Juniper advisory JSA106008 for platform-specific guidance and any operational workarounds.
  • Prioritize routers running IS-IS with adjacencies outside tightly trusted infrastructure.

Validation and detection

  • Inventory Junos OS and Junos OS Evolved devices and compare versions against affected ranges.
  • Confirm whether IS-IS is enabled and which neighbors can form adjacencies.
  • Monitor rpd memory usage as described in the Juniper advisory.
  • Review logs and telemetry for rpd crashes or repeated memory growth.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-401: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-21909 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (4.0)
Known Exploited
No
Published

Vector: 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/AU:Y/R:A/V:C/RE:M/U:Green

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 4.0HighCVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/V:C/RE:M/U:Green——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

7.1High
CVSS 4.0 vector shape for CVE-2026-21909Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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/AU:Y/R:A/V:C/RE:M/U:Green

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksJunos OS23.2, 23.4, 24.1, 0unaffected
Juniper NetworksJunos OS Evolved23.2, 23.4, 24.1, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-401 · source CWE mapping

Missing Release of Memory after Effective Lifetime

Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.