LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21913: Junos OS: EX4000: A high volume of traffic destined to the device leads to a crash and restart

An Incorrect Initialization of Resource vulnerability in the Internal Device Manager (IDM) of Juniper Networks Junos OS on EX4000 models allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS). On EX4000 models with 48 ports (EX4000-48T, EX4000-48P, EX4000-48MP) a high volume of traffic destined to the device will cause an FXPC crash and restart, which leads to a complete service outage until the device has automatically restarted. The following reboot reason can be seen in the output of 'show chassis routing-engine' and as a log message:   reason=0x4000002 reason_string=0x4000002:watchdog + panic with core dump This issue affects Junos OS on EX4000-48T, EX4000-48P and EX4000-48MP: * 24.4 versions before 24.4R2, * 25.2 versions before 25.2R1-S2, 25.2R2. This issue does not affect versions before 24.4R1 as the first Junos OS version for the EX4000 models was 24.4R1.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-21913 can make certain Juniper EX4000 48-port switches crash and restart when they receive a high volume of traffic aimed at the device itself. This creates a full service outage until the switch automatically restarts. The issue is unauthenticated and network-reachable, so exposed management or device-facing interfaces increase business risk.

Executive priority

Prioritize remediation for affected switches supporting critical networks, data centers, or high-availability paths. This is a denial-of-service issue, not a disclosed data theft issue, but outages could be material if these switches carry production traffic.

Technical view

Juniper describes an Incorrect Initialization of Resource flaw in Junos OS Internal Device Manager on EX4000-48T, EX4000-48P, and EX4000-48MP. A high volume of traffic destined to the device can crash and restart the FXPC. Affected releases are 24.4 before 24.4R2 and 25.2 before 25.2R1-S2 or 25.2R2. CVSS v4.0 score is 8.7.

Likely exposure

Organizations using EX4000 48-port models on affected Junos OS releases are exposed. The sources do not indicate impact to EX4000 models outside EX4000-48T, EX4000-48P, or EX4000-48MP, and versions before 24.4R1 are stated as unaffected because EX4000 support began at 24.4R1.

Exploitation context

The attack is network-based, unauthenticated, and requires high-volume traffic directed at the device. The reported impact is denial of service through FXPC crash and restart. The source bundle does not report active exploitation, and the CVE is not marked in KEV.

Researcher notes

The evidence is limited to CVE and Juniper advisory details in the provided bundle. No public exploit status, workaround beyond upgrading, or broader product impact is cited. Validate exact model and release before assessing exposure.

Mitigation direction

  • Upgrade affected EX4000-48T, EX4000-48P, and EX4000-48MP devices to a fixed Junos OS release.
  • For 24.4 deployments, move to 24.4R2 or later per Juniper guidance.
  • For 25.2 deployments, move to 25.2R1-S2, 25.2R2, or later per Juniper guidance.
  • Restrict unnecessary traffic destined to switch control or management interfaces where operationally feasible.
  • Monitor Juniper advisory JSA106014 for any updated workaround or release guidance.

Validation and detection

  • Inventory EX4000 48-port models and record current Junos OS versions.
  • Confirm whether any devices run 24.4 before 24.4R2 or 25.2 before fixed releases.
  • Review device logs for the documented watchdog panic and core dump reboot reason.
  • Check for recent unexplained FXPC crashes, restarts, or full switch service outages.
  • Verify remediated devices report a fixed Junos OS version after upgrade.
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-1419: 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-21913 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
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/RE:M

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
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/RE:M——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

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

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/RE:M

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 OS24.4, 25.2, 0unaffected
Weakness

CWE details

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

CWE-1419 · source CWE mapping

Incorrect Initialization of Resource

Incorrect Initialization of Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.