LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21906: Junos OS: SRX Series: With GRE performance acceleration enabled, receipt of a specific ICMP packet causes the PFE to crash

An Improper Handling of Exceptional Conditions vulnerability in the packet forwarding engine (PFE) of Juniper Networks Junos OS on SRX Series allows an unauthenticated network-based attacker sending a specific ICMP packet through a GRE tunnel to cause the PFE to crash and restart. When PowerMode IPsec (PMI) and GRE performance acceleration are enabled and the device receives a specific ICMP packet, a crash occurs in the SRX PFE, resulting in traffic loss. PMI is enabled by default, and GRE performance acceleration can be enabled by running the configuration command shown below. PMI is a mode of operation that provides IPsec performance improvements using Vector Packet Processing. Note that PMI with GRE performance acceleration is only supported on specific SRX platforms. This issue affects Junos OS on the SRX Series: * all versions before 21.4R3-S12,  * from 22.4 before 22.4R3-S8,  * from 23.2 before 23.2R2-S5,  * from 23.4 before 23.4R2-S5,  * from 24.2 before 24.2R2-S3,  * from 24.4 before 24.4R2-S1,  * from 25.2 before 25.2R1-S1, 25.2R2.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability can make certain Juniper SRX firewalls briefly stop forwarding traffic. If a vulnerable SRX has GRE performance acceleration enabled, a specially formed ICMP packet through a GRE tunnel can crash and restart the packet forwarding engine. The business impact is service disruption, not data theft, based on the provided sources.

Executive priority

Treat as high priority for network teams operating Juniper SRX with GRE tunnels. The main risk is outage or degraded connectivity. Patch exposed devices during the next urgent maintenance window, prioritizing internet- or partner-facing GRE paths and critical business traffic.

Technical view

CVE-2026-21906 is a Junos OS SRX Series improper handling issue in the PFE. With PowerMode IPsec and GRE performance acceleration enabled, receipt of a specific ICMP packet through a GRE tunnel can trigger a PFE crash and restart. Juniper rates it CVSS 4.0 8.7. Affected releases are fixed in the listed Junos maintenance versions.

Likely exposure

Exposure appears limited to Juniper SRX Series devices running affected Junos OS releases where PMI and GRE performance acceleration are in use on supported platforms. PMI is enabled by default, while GRE performance acceleration requires configuration. Devices without this feature combination are less likely to be exposed based on the advisory.

Exploitation context

The advisory describes unauthenticated, network-based denial of service causing PFE restart and traffic loss. The provided data does not show CISA KEV listing or public active exploitation. Exploitation requires traffic through a GRE tunnel and the relevant acceleration configuration.

Researcher notes

The vulnerability is availability-focused: VA:H and SA:L in CVSS 4.0, with no confidentiality or integrity impact reported. Evidence is from Juniper and CVE sources. The exact triggering packet details are not provided here and should not be inferred. Confirm exposure by feature state, platform support, and release train.

Mitigation direction

  • Upgrade affected SRX devices to Juniper’s fixed Junos OS releases listed in JSA106005.
  • Prioritize SRX devices using GRE tunnels and GRE performance acceleration.
  • Review Juniper’s advisory for platform-specific support and any updated workaround guidance.
  • If immediate upgrade is not possible, assess whether GRE performance acceleration is required.

Validation and detection

  • Inventory SRX Series devices and record Junos OS versions.
  • Compare versions against the affected and fixed release ranges in JSA106005.
  • Check whether PMI and GRE performance acceleration are enabled on each device.
  • Identify SRX platforms where PMI with GRE performance acceleration is supported.
  • Monitor for unexpected PFE crashes, restarts, or related traffic loss.
Prepared
Confidence
high
Sources
5

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-755: 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-21906 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/V:C/RE:M/U:Red

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
4Source 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/V:C/RE:M/U:Red——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-21906Attack 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/V:C/RE:M/U:Red

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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksJunos OS0, 22.4, 23.2, 23.4, 24.2, 24.4, 25.2unaffected
Weakness

CWE details

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

CWE-755 · source CWE mapping

Improper Handling of Exceptional Conditions

Improper Handling of Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.