<?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://vulnerability.circl.lu</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>Fri, 02 Oct 2026 18:06:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-42041 — Axios: Authentication Bypass via Prototype Pollution Gadget in `validateStatus` Merge Strategy</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-42041</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; axios, Red Hat HawtIO HawtIO 4.4.0, Red Hat Data Grid 8.6.1, Red Hat multicluster engine for Kubernetes 2.1, Red Hat multicluster engine for Kubernetes 2.11, Red Hat multicluster engine for Kubernetes 2.6, Red Hat multicluster engine for Kubernetes 2.8, Red Hat multicluster engine for Kubernetes 2.9, Red Hat Network Observability (NETOBSERV) 1.11.0, Red Hat Advanced Cluster Management for Kubernetes 2.14 and 50 more&lt;/p&gt;
&lt;p&gt;Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, the Axios library is vulnerable to a Prototype Pollution &amp;#34;Gadget&amp;#34; attack that allows any Object.prototype pollution to silently suppress all HTTP error responses (401, 403, 500, etc.), causing them to be treated as successful responses. This completely bypasses application-level authentication and error handling. The root cause is that validateStatus is the only config property using the mergeDirectKeys merge strategy, which uses JavaScript&amp;#39;s in operator — an operator that inherently traverses the prototype chain. When Object.prototype.validateStatus is polluted with () =&amp;gt; true, all HTTP status codes are accepted as success. This vulnerability is fixed in 1.15.1 and 0.31.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; axios, Red Hat HawtIO HawtIO 4.4.0, Red Hat Data Grid 8.6.1, Red Hat multicluster engine for Kubernetes 2.1, Red Hat multicluster engine for Kubernetes 2.11, Red Hat multicluster engine for Kubernetes 2.6, Red Hat multicluster engine for Kubernetes 2.8, Red Hat multicluster engine for Kubernetes 2.9, Red Hat Network Observability (NETOBSERV) 1.11.0, Red Hat Advanced Cluster Management for Kubernetes 2.14 and 50 more&lt;/p&gt;
&lt;p&gt;Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.1 and 0.31.1, the Axios library is vulnerable to a Prototype Pollution &amp;#34;Gadget&amp;#34; attack that allows any Object.prototype pollution to silently suppress all HTTP error responses (401, 403, 500, etc.), causing them to be treated as successful responses. This completely bypasses application-level authentication and error handling. The root cause is that validateStatus is the only config property using the mergeDirectKeys merge strategy, which uses JavaScript&amp;#39;s in operator — an operator that inherently traverses the prototype chain. When Object.prototype.validateStatus is polluted with () =&amp;gt; true, all HTTP status codes are accepted as success. This vulnerability is fixed in 1.15.1 and 0.31.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-42041</guid>
    </item>
  </channel>
</rss>
