Skip to content
VulniPulse
Advisory severityMedium5.8Red Hat Linux

Medium [CVE-2026-67315] NO_PROXY bypass allows exposure of local services

This medium-severity Red Hat Linux advisory covers CVE-2026-67315 affecting Red Hat Hardened Images, Migration Toolkit for Applications 8, Migration Toolkit for Containers.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-67315 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

axios versions 0.31.0 before 0.33.0 and 1.15.0 before 1.18.0 fail to recognize 0.0.0.0 as a loopback address in shouldBypassProxy.js, allowing requests to 0.0.0.0 to bypass NO_PROXY rules. Attackers can supply 0.0.0.0 URLs to route requests through configured proxies, potentially exposing local services when the proxy can reach the destination.

A flaw was found in axios. This vulnerability occurs because the software fails to correctly identify 0.0.0.0 as a local loopback address when evaluating NO_PROXY rules.

A remote attacker could exploit this by providing a 0.0.0.0 URL, causing requests to bypass intended proxy restrictions. This could lead to the exposure of internal services to the configured proxy, potentially allowing unauthorized access to local resources.

Red Hat severity: Moderate — CVSS 5.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N). Weakness: CWE-115.

Affected products named by the advisory: Red Hat Hardened Images; Migration Toolkit for Applications 8; Migration Toolkit for Containers; Multicluster Engine for Kubernetes; and 15 more.

Affected versions
  • < 0.31.0
  • < 0.33.0
  • < 1.15.0
  • < 1.18.0
  • < 0.0.0.0

Official advisory · high-confidence parse· fetched 5 days ago·verify at source

Fixed versions
  • grafana13-1-main-13.1.1-0.5.hum1
  • grafana13-1-main-13.1.1-0.5.2.hum1
  • RHSA-2026:49714
  • RHSA-2026:50826

Official advisory · high-confidence parse· fetched 5 days ago·verify at source

Mitigation

Upgrade to a fixed release: grafana13-1-main-13.1.1-0.5.hum1, grafana13-1-main-13.1.1-0.5.2.hum1, RHSA-2026:49714, RHSA-2026:50826. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 5 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.