Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Unrated

Node.js proxy tunnel error message credential leak

IdentifiersCVE-2026-48615CWE-532

CVE-2026-48615 is a medium-severity information disclosure vulnerability in Node.js affecting proxy tunnel error handling. When Node.js encounters an ERR_PROXY_TUNNEL condition while using an HTTP proxy tunnel, proxy credentials embedded in the proxy URL may be included in the generated error message. As a result, usernames, passwords, or other proxy authentication material can be exposed through logs, diagnostic output, exception traces, or other error-reporting channels. The issue affects the supported Node.js 22.x, 24.x, and 26.x release lines.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in disclosure of sensitive proxy credentials. If affected applications log or otherwise expose ERR_PROXY_TUNNEL messages, attackers or unauthorized users with access to logs, monitoring systems, crash reports, or application output may recover proxy authentication secrets. This can enable subsequent unauthorized use of the proxy service and potentially facilitate further access depending on how those credentials are reused.

Mitigation

If you can’t patch tonight, do this now.

Avoid embedding credentials directly in proxy URLs where possible. Sanitize or suppress ERR_PROXY_TUNNEL and related exception output before logging or returning it to users. Restrict access to application logs, diagnostics, and crash-reporting systems that may contain historical error messages. Rotate exposed proxy credentials if leakage is suspected.

Remediation

Patch, then assume compromise.

Upgrade Node.js to a fixed release. The provided content identifies fixed versions as v22.23.0, v24.17.0, and v26.3.1 in the June 18, 2026 security release; the content also references later patched versions v22.23.1, v24.17.1, and v26.3.2. Use the latest available patched release in the relevant supported branch.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.