Is this vulnerability remotely exploitable?

Yes, in many architectures it can be. If a remote attacker can influence or control the URL used in Axios requests (for example, via parameters, redirect targets, or configuration options), they can attempt to bypass NO_PROXY and trigger proxied requests to local or internal addresses. If the URL cannot be influenced from outside, the exposure is reduced to internal or supply-chain actors.

Does exploitation require authentication or local access?

It depends on how Axios is used. If the service exposes URL-influencing functionality only to authenticated users, then an attacker typically needs valid credentials or must compromise an authenticated context. In other cases, such as public-facing APIs that accept arbitrary URLs or redirect destinations, exploitation can be unauthenticated and purely remote.

What is the safest general fix pattern?

The safest pattern is to decouple trust in NO_PROXY from critical security boundaries and enforce strict destination controls: treat the entire loopback and internal IP ranges as off-limits for any Axios requests that derive from user-controlled input, normalize and validate all target hosts and IPs before issuing requests, and enforce explicit allow-lists or deny-lists at both application and network layers. Combined with corrected NO_PROXY logic, this significantly reduces the risk of proxy bypass and SSRF.

Severity:

HIGH RISK

(7.2)

NO_PROXY Bypass via Local Address Manipulation (CWE-918) in Axios HTTP Client

CVE-2026-42043

Published:

Apr 24, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-74;CWE-89

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

Database Compromise and Data Integrity Loss

April 27, 2026

CWE-863

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Privilege Escalation and Unauthorized Session Control

April 27, 2026

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF) / Proxy Bypass

CWE:

CWE-183;CWE-441;CWE-918

Impact:

Proxy Bypass leading to Potential SSRF and Internal Service Exposure

Severity:

HIGH RISK

(7.2)

CVSS Version:

3.1

Vulnerability Type

Category:

Server-Side Request Forgery (SSRF) / Proxy Bypass

CWE:

CWE-183;CWE-441;CWE-918

Impact:

Proxy Bypass leading to Potential SSRF and Internal Service Exposure

Severity:

HIGH RISK

(7.2)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

NO_PROXY Bypass via Local Address Manipulation (CWE-918) in Axios HTTP Client

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare