CVE-2026-57030: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in Juniper Networks Junos OS
A race condition vulnerability (CWE-362) exists in the packet forwarding engine of Juniper Networks Junos OS on SRX Series devices. This flaw allows an unauthenticated network attacker to cause a denial-of-service by manipulating flow timeout values, leading to accumulation of invalidated sessions that cannot be cleared manually. The resulting impact can cause forwarding to stop or trigger a system reboot due to a flowd core. The issue affects specific Junos OS versions 24.2 before 24.2R2-S3, 24.4 before 24.4R2-S1 and S2, and 25.2 before 25.2R1-S2 and 25.2R2. Versions earlier than 24.2R1 are not affected. The CVSS score is 5.9 (medium severity).
AI Analysis
Technical Summary
CVE-2026-57030 is a race condition vulnerability in the packet forwarding engine of Juniper Networks Junos OS on SRX Series devices. During flow removal, a race condition can cause the flow timeout to be set incorrectly to a very high value (>10,000 seconds) instead of the intended 3 seconds. This leads to an accumulation of invalidated sessions that cannot be cleared manually, causing denial-of-service by stopping forwarding or triggering a flowd core and automatic reboot. The vulnerability affects Junos OS versions 24.2 prior to 24.2R2-S3, 24.4 prior to 24.4R2-S1 and 24.4R2-S2, and 25.2 prior to 25.2R1-S2 and 25.2R2. Releases earlier than 24.2R1 are not affected. A patch is available as this is a cloud-managed service, and Juniper manages remediation server-side.
Potential Impact
An unauthenticated network attacker can exploit this race condition to cause denial-of-service on SRX Series devices by causing flow timeouts to be set incorrectly, leading to an accumulation of invalidated sessions. This accumulation cannot be cleared manually and results in forwarding stoppage or a flowd core crash causing automatic reboot. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
Juniper manages remediation for this cloud-hosted service and has made patches available for the affected versions. Users should ensure their devices are updated to versions 24.2R2-S3 or later, 24.4R2-S2 or later, and 25.2R2 or later to mitigate this vulnerability. Check the official Juniper advisory for the latest patch and update instructions. No additional manual mitigation is required as the vendor handles patching for the cloud service.
CVE-2026-57030: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in Juniper Networks Junos OS
Description
A race condition vulnerability (CWE-362) exists in the packet forwarding engine of Juniper Networks Junos OS on SRX Series devices. This flaw allows an unauthenticated network attacker to cause a denial-of-service by manipulating flow timeout values, leading to accumulation of invalidated sessions that cannot be cleared manually. The resulting impact can cause forwarding to stop or trigger a system reboot due to a flowd core. The issue affects specific Junos OS versions 24.2 before 24.2R2-S3, 24.4 before 24.4R2-S1 and S2, and 25.2 before 25.2R1-S2 and 25.2R2. Versions earlier than 24.2R1 are not affected. The CVSS score is 5.9 (medium severity).
CVSS v3.1
Score 5.9medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-57030 is a race condition vulnerability in the packet forwarding engine of Juniper Networks Junos OS on SRX Series devices. During flow removal, a race condition can cause the flow timeout to be set incorrectly to a very high value (>10,000 seconds) instead of the intended 3 seconds. This leads to an accumulation of invalidated sessions that cannot be cleared manually, causing denial-of-service by stopping forwarding or triggering a flowd core and automatic reboot. The vulnerability affects Junos OS versions 24.2 prior to 24.2R2-S3, 24.4 prior to 24.4R2-S1 and 24.4R2-S2, and 25.2 prior to 25.2R1-S2 and 25.2R2. Releases earlier than 24.2R1 are not affected. A patch is available as this is a cloud-managed service, and Juniper manages remediation server-side.
Potential Impact
An unauthenticated network attacker can exploit this race condition to cause denial-of-service on SRX Series devices by causing flow timeouts to be set incorrectly, leading to an accumulation of invalidated sessions. This accumulation cannot be cleared manually and results in forwarding stoppage or a flowd core crash causing automatic reboot. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
Juniper manages remediation for this cloud-hosted service and has made patches available for the affected versions. Users should ensure their devices are updated to versions 24.2R2-S3 or later, 24.4R2-S2 or later, and 25.2R2 or later to mitigate this vulnerability. Check the official Juniper advisory for the latest patch and update instructions. No additional manual mitigation is required as the vendor handles patching for the cloud service.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- juniper
- Date Reserved
- 2026-06-23T16:27:00.249Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Is Cloud Service
- true
Threat ID: 6a50171668715ace431ea20b
Added to database: 07/09/2026, 21:48:06 UTC
Last enriched: 07/09/2026, 22:03:42 UTC
Last updated: 07/09/2026, 23:59:38 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.