<?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>Thu, 08 Oct 2026 23:30:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-33774 — Junos OS: MX Series: Firewall filters on lo0.&lt;non-0&gt; in the default routing instance are not in effect</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-33774</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Juniper Networks Junos OS&lt;/p&gt;
&lt;p&gt;An Improper Check for Unusual or Exceptional Conditions vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on MX Series allows an unauthenticated, network-based attacker to bypass the configured firewall filter and access the control-plane of the device.&lt;/p&gt;
&lt;p&gt;On MX platforms with&lt;/p&gt;
&lt;p&gt;MPC10, MPC11, LC4800 or LC9600&lt;/p&gt;
&lt;p&gt;line cards, and MX304, firewall filters applied on a loopback interface lo0.n (where n is a non-0 number) don&amp;#39;t get executed when lo0.n is in the global VRF / default routing-instance.&lt;/p&gt;
&lt;p&gt;An affected configuration would be:&lt;/p&gt;
&lt;p&gt;user@host# show configuration interfaces lo0 | display set
set interfaces lo0 unit 1 family inet filter input &amp;lt;filter-name&amp;gt;&lt;/p&gt;
&lt;p&gt;where a firewall filter is applied to a non-0 loopback interface, but that loopback interface is not referred to in any routing-instance (RI) configuration, which implies that it&amp;#39;s used in the default RI.&lt;/p&gt;
&lt;p&gt;The issue can be observed with the CLI command:&lt;/p&gt;
&lt;p&gt;user@device&amp;gt; show firewall counter filter &amp;lt;filter_name&amp;gt;&lt;/p&gt;
&lt;p&gt;not showing any matches.&lt;/p&gt;
&lt;p&gt;This issue affects Junos OS on MX Series:&lt;/p&gt;
&lt;p&gt;*  all versions before 23.2R2-S6,
  *  23.4 versions before 23.4R2-S7,
  *  24.2 versions before 24.2R2,
  *  24.4 versions before 24.4R2.&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;An Improper Check for Unusual or Exceptional Conditions vulnerability in the packet forwarding engine (pfe) of Juniper Networks Junos OS on MX Series allows an unauthenticated, network-based attacker to bypass the configured firewall filter and access the control-plane of the device.&lt;/p&gt;
&lt;p&gt;On MX platforms with&lt;/p&gt;
&lt;p&gt;MPC10, MPC11, LC4800 or LC9600&lt;/p&gt;
&lt;p&gt;line cards, and MX304, firewall filters applied on a loopback interface lo0.n (where n is a non-0 number) don&amp;#39;t get executed when lo0.n is in the global VRF / default routing-instance.&lt;/p&gt;
&lt;p&gt;An affected configuration would be:&lt;/p&gt;
&lt;p&gt;user@host# show configuration interfaces lo0 | display set
set interfaces lo0 unit 1 family inet filter input &amp;lt;filter-name&amp;gt;&lt;/p&gt;
&lt;p&gt;where a firewall filter is applied to a non-0 loopback interface, but that loopback interface is not referred to in any routing-instance (RI) configuration, which implies that it&amp;#39;s used in the default RI.&lt;/p&gt;
&lt;p&gt;The issue can be observed with the CLI command:&lt;/p&gt;
&lt;p&gt;user@device&amp;gt; show firewall counter filter &amp;lt;filter_name&amp;gt;&lt;/p&gt;
&lt;p&gt;not showing any matches.&lt;/p&gt;
&lt;p&gt;This issue affects Junos OS on MX Series:&lt;/p&gt;
&lt;p&gt;*  all versions before 23.2R2-S6,
  *  23.4 versions before 23.4R2-S7,
  *  24.2 versions before 24.2R2,
  *  24.4 versions before 24.4R2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-33774</guid>
    </item>
  </channel>
</rss>
