https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 13:04:24 +0000 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0852 certfr-2026-avi-0852 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0852 https://cve.radiocsirt.org/vuln/euvd-2026-335626 EUVD-2026-335626 https://cve.radiocsirt.org/vuln/euvd-2026-335626 https://cve.radiocsirt.org/vuln/fkie_cve-2026-57030 <p>A Concurrent Execution using Shared Resource with Improper Synchronization (&#39;Race Condition&#39;) 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).</p> <p>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:</p> <p>user@host&gt; show security flow session | match timeout Session ID: 98784248524, Policy name: PROD-FLOW/4, HA State: Active, Timeout: 85250, Session State: Valid</p> <p>This will lead to an accumulation of flows which can be observed by an ever-increasing value of invalidated sessions in the output of &#39;show security flow session summary&#39;:</p> <p>user@host&gt; show security flow session summary | match invalid Invalidated sessions: 216931These sessions can&#39;t be cleared manually with the &#39;clear security flow session&#39; 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.</p> <p>This issue affects Junos OS on SRX Series:</p> <p>* 24.2 versions before…</p> <p>A Concurrent Execution using Shared Resource with Improper Synchronization (&#39;Race Condition&#39;) 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).</p> <p>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:</p> <p>user@host&gt; show security flow session | match timeout Session ID: 98784248524, Policy name: PROD-FLOW/4, HA State: Active, Timeout: 85250, Session State: Valid</p> <p>This will lead to an accumulation of flows which can be observed by an ever-increasing value of invalidated sessions in the output of &#39;show security flow session summary&#39;:</p> <p>user@host&gt; show security flow session summary | match invalid Invalidated sessions: 216931These sessions can&#39;t be cleared manually with the &#39;clear security flow session&#39; 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.</p> <p>This issue affects Junos OS on SRX Series:</p> <p>* 24.2 versions before…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-57030 https://cve.radiocsirt.org/vuln/ghsa-6hx5-3rjf-rm36 <p>A Concurrent Execution using Shared Resource with Improper Synchronization (&#39;Race Condition&#39;) 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).</p> <p>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:</p> <p>user@host&gt; show security flow session | match timeout Session ID: 98784248524, Policy name: PROD-FLOW/4, HA State: Active, Timeout: 85250, Session State: Valid</p> <p>This will lead to an accumulation of flows which can be observed by an ever-increasing value of invalidated sessions in the output of &#39;show security flow session summary&#39;:</p> <p>user@host&gt; show security flow session summary | match invalid Invalidated sessions: 216931These sessions can&#39;t be cleared manually with the &#39;clear security flow session&#39; 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.</p> <p>This issue affects Junos OS on SRX Series:</p> <p>* 24.2 versions before…</p> <p>A Concurrent Execution using Shared Resource with Improper Synchronization (&#39;Race Condition&#39;) 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).</p> <p>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:</p> <p>user@host&gt; show security flow session | match timeout Session ID: 98784248524, Policy name: PROD-FLOW/4, HA State: Active, Timeout: 85250, Session State: Valid</p> <p>This will lead to an accumulation of flows which can be observed by an ever-increasing value of invalidated sessions in the output of &#39;show security flow session summary&#39;:</p> <p>user@host&gt; show security flow session summary | match invalid Invalidated sessions: 216931These sessions can&#39;t be cleared manually with the &#39;clear security flow session&#39; 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.</p> <p>This issue affects Junos OS on SRX Series:</p> <p>* 24.2 versions before…</p> https://cve.radiocsirt.org/vuln/ghsa-6hx5-3rjf-rm36 https://cve.radiocsirt.org/vuln/ncsc-2026-0224 NCSC-2026-0224 https://cve.radiocsirt.org/vuln/ncsc-2026-0224 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2257 <p>Ein Angreifer kann mehrere Schwachstellen in Juniper JUNOS, JUNOS Evolved, Juniper EX Series, Juniper MX Series, Juniper QFX Series und Juniper SRX Series ausnutzen, um einen Denial of Service Zustand herbeizuführen, um Informationen offenzulegen, um Code auszuführen und um ein undefiniertes Verhalten auszulösen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Juniper JUNOS, JUNOS Evolved, Juniper EX Series, Juniper MX Series, Juniper QFX Series und Juniper SRX Series ausnutzen, um einen Denial of Service Zustand herbeizuführen, um Informationen offenzulegen, um Code auszuführen und um ein undefiniertes Verhalten auszulösen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2257