CVE-2026-21906: Junos OS: SRX Series: With GRE performance acceleration enabled, receipt of a specific ICMP packet causes the PFE to crash
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.54% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Juniper Networks Junos OS 21.4R3-S12, 22.4R3-S8, 23.2R2-S5.
Low priority for now. Upgrade to Juniper Networks Junos OS 21.4R3-S12, 22.4R3-S8, 23.2R2-S5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 15, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 45th percentile
- CWE
- CWE-755
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 34 / 40 · 8.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · juniper
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| juniper | srx4300 | cpe:2.3:h:juniper:srx4300 |
| juniper | junos | cpe:2.3:o:juniper:junos |
| juniper | srx1500 | cpe:2.3:h:juniper:srx1500 |
| juniper | srx1600 | cpe:2.3:h:juniper:srx1600 |
| juniper | srx2300 | cpe:2.3:h:juniper:srx2300 |
| juniper | srx300 | cpe:2.3:h:juniper:srx300 |
| juniper | srx320 | cpe:2.3:h:juniper:srx320 |
| juniper | srx340 | cpe:2.3:h:juniper:srx340 |
| juniper | srx345 | cpe:2.3:h:juniper:srx345 |
| juniper | srx380 | cpe:2.3:h:juniper:srx380 |
| juniper | srx4100 | cpe:2.3:h:juniper:srx4100 |
| juniper | srx4120 | cpe:2.3:h:juniper:srx4120 |
and 6 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper junosbefore 21.4
- juniper junos21.4
- juniper junos22.4
- juniper junos23.2
- juniper junos23.4
- juniper junos24.2
- juniper junos24.4
- juniper junos25.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (juniper). Independent of NVD's CPE analysis and usually ahead of it.
Juniper Networks Junos OS
- before 21.4R3-S12affected · semver
- 22.4 and later · before 22.4R3-S8affected · semver
- 23.2 and later · before 23.2R2-S5affected · semver
- 23.4 and later · before 23.4R2-S5affected · semver
- 24.2 and later · before 24.2R2-S3affected · semver
- 24.4 and later · before 24.4R2-S1affected · semver
- 25.2 and later · before 25.2R1-S1, 25.2R2affected · semver
Same product
juniper: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-36845Junos OS: EX and SRX Series: A PHP vulnerability in J-Web allows an unauthenticated to control an important environment variableKEV98Now
- CVE-2023-36846Junos OS: SRX Series: A vulnerability in J-Web allows an unauthenticated attacker to upload arbitrary filesKEV79This week
- CVE-2023-36844Junos OS: EX Series: A PHP vulnerability in J-Web allows an unauthenticated attacker to control important environment variablesKEV78This week
Published before and after this one in the same product
- ← EarlierCVE-2026-21903Jan 15, 2026 · Junos OS: Subscribing to telemetry sensors at scale causes all FPCs to crash28Monitor
- ← EarlierCVE-2026-21905Jan 15, 2026 · Junos OS: SRX Series, MX Series with MX-SPC3 or MS-MPC: Receipt of multiple specific SIP messages results in flow management process crash34Monitor
- Later →CVE-2026-21908Jan 15, 2026 · Junos OS and Junos OS Evolved: Use after free vulnerability In 802.1X authentication daemon can cause crash of the dot1xd process30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Juniper Networks Junos OS | 21.4R3-S12 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.4R3-S8 | Vendor (CNA) |
| Juniper Networks Junos OS | 23.2R2-S5 | Vendor (CNA) |
| Juniper Networks Junos OS | 23.4R2-S5 | Vendor (CNA) |
| Juniper Networks Junos OS | 24.2R2-S3 | Vendor (CNA) |
| Juniper Networks Junos OS | 24.4R2-S1 | Vendor (CNA) |
| Juniper Networks Junos OS | 25.2R1-S1, 25.2R2 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-39525463 days apartJunos OS and Junos OS Evolved: When BGP traceoptions is enabled, receipt of specially crafted BGP packet causes RPD crash34Monitor
- CVE-2025-52948188 days apartJunos OS: Specific unknown traffic pattern causes FPC and system to crash when packet capturing is enabled32Monitor
- CVE-2024-47491461 days apartJunos OS and Junos OS Evolved: Receipt of a specific malformed BGP path attribute leads to an RPD crash32Monitor
- CVE-2026-02030 days apartJunos OS: Receipt of a specifically malformed ICMP packet causes an FPC restart28Monitor
- CVE-2025-52947188 days apartJunos OS: ACX Series: When 'hot-standby' mode is configured for an L2 circuit, interface flap causes the FEB to crash28Monitor
- CVE-2025-21602371 days apartJunos OS and Junos OS Evolved: Receipt of specially crafted BGP update packet causes RPD crash28Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-755 · Improper Handling of Exceptional ConditionsCVSS 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/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:Red
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.