<?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://db.gcve.eu</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 15:40:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-62718 — Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF</title>
      <link>https://db.gcve.eu/vuln/cve-2025-62718</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; axios, Red Hat Ansible Automation Platform 2.5 for RHEL 8, Red Hat Ansible Automation Platform 2.5 for RHEL 9, Red Hat Streams for Apache Kafka 3.2.0, Red Hat Cluster Observability Operator 1.5.0, Red Hat multicluster engine for Kubernetes 2.6, Red Hat multicluster engine for Kubernetes 2.8, Red Hat Network Observability (NETOBSERV) 1.11.0, Red Hat Advanced Cluster Management for Kubernetes 2.14, Red Hat Advanced Cluster Security 4.9 and 53 more&lt;/p&gt;
&lt;p&gt;Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.0 and 0.31.0, Axios does not correctly handle hostname normalization when checking NO_PROXY rules. Requests to loopback addresses like localhost. (with a trailing dot) or [::1] (IPv6 literal) skip NO_PROXY matching and go through the configured proxy. This goes against what developers expect and lets attackers force requests through a proxy, even if NO_PROXY is set up to protect loopback or internal services. This issue leads to the possibility of proxy bypass and SSRF vulnerabilities allowing attackers to reach sensitive loopback or internal services despite the configured protections. This vulnerability is fixed in 1.15.0 and 0.31.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; axios, Red Hat Ansible Automation Platform 2.5 for RHEL 8, Red Hat Ansible Automation Platform 2.5 for RHEL 9, Red Hat Streams for Apache Kafka 3.2.0, Red Hat Cluster Observability Operator 1.5.0, Red Hat multicluster engine for Kubernetes 2.6, Red Hat multicluster engine for Kubernetes 2.8, Red Hat Network Observability (NETOBSERV) 1.11.0, Red Hat Advanced Cluster Management for Kubernetes 2.14, Red Hat Advanced Cluster Security 4.9 and 53 more&lt;/p&gt;
&lt;p&gt;Axios is a promise based HTTP client for the browser and Node.js. Prior to 1.15.0 and 0.31.0, Axios does not correctly handle hostname normalization when checking NO_PROXY rules. Requests to loopback addresses like localhost. (with a trailing dot) or [::1] (IPv6 literal) skip NO_PROXY matching and go through the configured proxy. This goes against what developers expect and lets attackers force requests through a proxy, even if NO_PROXY is set up to protect loopback or internal services. This issue leads to the possibility of proxy bypass and SSRF vulnerabilities allowing attackers to reach sensitive loopback or internal services despite the configured protections. This vulnerability is fixed in 1.15.0 and 0.31.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-62718</guid>
    </item>
    <item>
      <title>USN-8638-1 — node-axios vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8638-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: node-axios, Ubuntu:Pro:22.04:LTS: node-axios, Ubuntu:Pro:24.04:LTS: node-axios, Ubuntu:Pro:26.04:LTS: node-axios&lt;/p&gt;
&lt;p&gt;Ameer Assadi discovered that Axios did not properly handle certain
hostnames when applying NO_PROXY rules. An attacker could possibly use
this issue to bypass proxy restrictions and access internal services,
resulting in server-side request forgery. (CVE-2025-62718)&lt;/p&gt;
&lt;p&gt;It was discovered that Axios did not properly protect certain HTTP
header values from prototype pollution. An attacker could possibly use
this issue to inject malicious values into outbound requests, resulting
in HTTP header injection. (CVE-2026-40175)&lt;/p&gt;
&lt;p&gt;Sachin Patil and Amol Patil discovered that Axios did not properly apply
NO_PROXY rules to certain loopback addresses. An attacker could possibly
use this issue to bypass proxy restrictions and access internal
services, resulting in server-side request forgery. (CVE-2026-42043)&lt;/p&gt;
&lt;p&gt;Yu Bao discovered that Axios did not properly protect JSON response
processing from prototype pollution. An attacker could possibly use this
issue to modify values in application responses, resulting in
authorization bypass or privilege escalation. This issue only affected
Ubuntu 26.04 LTS. (CVE-2026-42044)&lt;/p&gt;
&lt;p&gt;It was discovered that Axios did not properly protect certain request
configuration options from prototype pollution. An attacker could
possibly use this issue to modify outbound HTTP requests, resulting in
security restrictions being bypassed. This issue only affected Ubuntu
24.04 LTS and Ubuntu 26.04 LTS. (CVE-2026-42264)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: node-axios, Ubuntu:Pro:22.04:LTS: node-axios, Ubuntu:Pro:24.04:LTS: node-axios, Ubuntu:Pro:26.04:LTS: node-axios&lt;/p&gt;
&lt;p&gt;Ameer Assadi discovered that Axios did not properly handle certain
hostnames when applying NO_PROXY rules. An attacker could possibly use
this issue to bypass proxy restrictions and access internal services,
resulting in server-side request forgery. (CVE-2025-62718)&lt;/p&gt;
&lt;p&gt;It was discovered that Axios did not properly protect certain HTTP
header values from prototype pollution. An attacker could possibly use
this issue to inject malicious values into outbound requests, resulting
in HTTP header injection. (CVE-2026-40175)&lt;/p&gt;
&lt;p&gt;Sachin Patil and Amol Patil discovered that Axios did not properly apply
NO_PROXY rules to certain loopback addresses. An attacker could possibly
use this issue to bypass proxy restrictions and access internal
services, resulting in server-side request forgery. (CVE-2026-42043)&lt;/p&gt;
&lt;p&gt;Yu Bao discovered that Axios did not properly protect JSON response
processing from prototype pollution. An attacker could possibly use this
issue to modify values in application responses, resulting in
authorization bypass or privilege escalation. This issue only affected
Ubuntu 26.04 LTS. (CVE-2026-42044)&lt;/p&gt;
&lt;p&gt;It was discovered that Axios did not properly protect certain request
configuration options from prototype pollution. An attacker could
possibly use this issue to modify outbound HTTP requests, resulting in
security restrictions being bypassed. This issue only affected Ubuntu
24.04 LTS and Ubuntu 26.04 LTS. (CVE-2026-42264)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8638-1</guid>
    </item>
  </channel>
</rss>
