<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 11:32:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-57030 — Junos OS: SRX Series: Flow sessions are not getting cleared leading to a DoS</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-57030</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Juniper Networks Junos OS&lt;/p&gt;
&lt;p&gt;A Concurrent Execution using Shared Resource with Improper Synchronization (&amp;#39;Race Condition&amp;#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).&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;user@host&amp;gt; show security flow session | match timeout
Session ID: 98784248524, Policy name: PROD-FLOW/4, HA State: Active, Timeout: 85250, Session State: Valid&lt;/p&gt;
&lt;p&gt;This will lead to an accumulation of flows which can be observed by an ever-increasing value of invalidated sessions in the output of &amp;#39;show security flow session summary&amp;#39;:&lt;/p&gt;
&lt;p&gt;user@host&amp;gt; show security flow session summary | match invalid
Invalidated sessions: 216931These sessions can&amp;#39;t be cleared manually with the &amp;#39;clear security flow session&amp;#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.&lt;/p&gt;
&lt;p&gt;This issue affects Junos OS on SRX Series:&lt;/p&gt;
&lt;p&gt;*  24.2 versions before…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Juniper Networks Junos OS&lt;/p&gt;
&lt;p&gt;A Concurrent Execution using Shared Resource with Improper Synchronization (&amp;#39;Race Condition&amp;#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).&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;user@host&amp;gt; show security flow session | match timeout
Session ID: 98784248524, Policy name: PROD-FLOW/4, HA State: Active, Timeout: 85250, Session State: Valid&lt;/p&gt;
&lt;p&gt;This will lead to an accumulation of flows which can be observed by an ever-increasing value of invalidated sessions in the output of &amp;#39;show security flow session summary&amp;#39;:&lt;/p&gt;
&lt;p&gt;user@host&amp;gt; show security flow session summary | match invalid
Invalidated sessions: 216931These sessions can&amp;#39;t be cleared manually with the &amp;#39;clear security flow session&amp;#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.&lt;/p&gt;
&lt;p&gt;This issue affects Junos OS on SRX Series:&lt;/p&gt;
&lt;p&gt;*  24.2 versions before…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-57030</guid>
    </item>
  </channel>
</rss>
