As part of the stateful traffic processing on SRX Series devices flows are being established, and removed when not needed anymore. During the removal process the timeout of a flow should be set to 3 seconds and consequentially the flow should be removed shortly after. Due to a race condition occurring when setting the timeout there is a chance (the exact conditions are outside the attackers control) that the timeout is instead set to a very high value of larger than 10,000 seconds:
user@host> show security flow session | match timeout
Session ID: 98784248524, Policy name: PROD-FLOW/4, HA State: Active, Timeout: 85250, Session State: Valid
This will lead to an accumulation of flows which can be observed by an ever-increasing value of invalidated sessions in the output of 'show security flow session summary':
user@host> show security flow session summary | match invalid
Invalidated sessions: 216931These sessions can't be cleared manually with the 'clear security flow session' command, which will either lead to forwarding to stop (and the system needs to be manually recovered with a reboot) or to a flowd core and automatic reboot.
This issue affects Junos OS on SRX Series:
* 24.2 versions before 24.2R2-S3,
* 24.4 versions before 24.4R2-S1, 24.4R2-S2,
* 25.2 versions before 25.2R1-S2, 25.2R2.
This issue does not affect releases earlier than 24.2R1;
Project Subscriptions
| Vendors | Products |
|---|---|
|
Juniper
Subscribe
|
Junos
Subscribe
Srx1500
Subscribe
Srx1600
Subscribe
Srx2300
Subscribe
Srx300
Subscribe
Srx320
Subscribe
Srx340
Subscribe
Srx345
Subscribe
Srx380
Subscribe
Srx400
Subscribe
Srx4100
Subscribe
Srx4120
Subscribe
Srx4200
Subscribe
Srx4300
Subscribe
Srx440
Subscribe
Srx4600
Subscribe
Srx4700
Subscribe
Srx5400
Subscribe
Srx5600
Subscribe
Srx5800
Subscribe
|
|
Juniper Networks
Subscribe
|
Junos Os
Subscribe
|
No advisories yet.
Solution
The following software releases have been updated to resolve this specific issue: Junos OS: 24.2R2-S3, 24.4R2-S1, 25.2R1-S2, 25.2R2, 25.4R1, and all subsequent releases.
Workaround
There are no known workarounds for this issue.
| Link | Providers |
|---|---|
| https://supportportal.juniper.net/JSA110090 |
|
Thu, 09 Jul 2026 23:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Juniper Networks
Juniper Networks junos Os |
|
| Vendors & Products |
Juniper Networks
Juniper Networks junos Os |
Thu, 09 Jul 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') vulnerability in the packet forwarding engine (PFE) of Juniper Networks Junos OS on SRX Series allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS). As part of the stateful traffic processing on SRX Series devices flows are being established, and removed when not needed anymore. During the removal process the timeout of a flow should be set to 3 seconds and consequentially the flow should be removed shortly after. Due to a race condition occurring when setting the timeout there is a chance (the exact conditions are outside the attackers control) that the timeout is instead set to a very high value of larger than 10,000 seconds: user@host> show security flow session | match timeout Session ID: 98784248524, Policy name: PROD-FLOW/4, HA State: Active, Timeout: 85250, Session State: Valid This will lead to an accumulation of flows which can be observed by an ever-increasing value of invalidated sessions in the output of 'show security flow session summary': user@host> show security flow session summary | match invalid Invalidated sessions: 216931These sessions can't be cleared manually with the 'clear security flow session' command, which will either lead to forwarding to stop (and the system needs to be manually recovered with a reboot) or to a flowd core and automatic reboot. This issue affects Junos OS on SRX Series: * 24.2 versions before 24.2R2-S3, * 24.4 versions before 24.4R2-S1, 24.4R2-S2, * 25.2 versions before 25.2R1-S2, 25.2R2. This issue does not affect releases earlier than 24.2R1; | |
| Title | Junos OS: SRX Series: Flow sessions are not getting cleared leading to a DoS | |
| Weaknesses | CWE-362 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: juniper
Published:
Updated: 2026-07-10T14:43:39.183Z
Reserved: 2026-06-23T16:27:00.249Z
Link: CVE-2026-57030
No data.
Status : Analyzed
Published: 2026-07-09T22:17:08.643
Modified: 2026-07-13T20:16:07.750
Link: CVE-2026-57030
No data.
OpenCVE Enrichment
Updated: 2026-08-01T14:00:06Z