CVE-2026-48615: Proxy credentials leaked in ERR_PROXY_TUNNEL error message

Published Jun 18, 2026
·
Updated

A flaw in Node.js proxy tunnel error handling could expose proxy credentials in ERRPROXYTUNNEL 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.

Other sources

A flaw in Node.js proxy tunnel error handling could expose proxy credentials in ERRPROXYTUNNEL 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.

— Node.Js

Affected Software

10 affected componentsFixes available
nodejs=22
nodejs=24
nodejs=26
Nodejs Node.js=22.22.3
Nodejs Node.js=24.16.0
Nodejs Node.js=26.3.0
Node.js Node.js>=22.0.0<22.23.0, >=24.0.0<24.17.0, >=26.0.0<26.3.1
22.23.024.17.026.3.1
Node.js Node.js>=22.0.0<22.23.0
22.23.0
Node.js Node.js>=24.0.0<24.17.0
24.17.0
Node.js Node.js>=26.0.0<26.3.1
26.3.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 22.23.0Fixed in 24.17.0Fixed in 26.3.1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 22.23.0
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 24.17.0
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 26.3.1

Event History

Jun 18, 2026
CVE Published
via Node.js·04:00 AM
Data Sourced
via Node.js·04:00 AM
DescriptionSeverityAffected Software
Jun 26, 2026
CVE Published
via MITRE·01:14 AM
Data Sourced
via MITRE·01:14 AM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·02:02 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·02:16 AM
RemedyDescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-48615?

The severity of CVE-2026-48615 is rated as high with a CVSS score of 7.5.

2

How do I fix CVE-2026-48615?

To mitigate CVE-2026-48615, ensure to sanitize proxy URLs to avoid exposing credentials and update to the latest Node.js version where the issue has been addressed.

3

What type of exposure risk is associated with CVE-2026-48615?

CVE-2026-48615 poses a risk of exposing sensitive proxy credentials through error messages that may be logged or retrievable by user actions.

4

In which version of Node.js does CVE-2026-48615 exist?

CVE-2026-48615 affects specific versions of Node.js prior to the updates that address this vulnerability.

5

What are the potential impacts of CVE-2026-48615?

The potential impact of CVE-2026-48615 includes unauthorized access to proxy credentials, which could lead to further exploitation of systems using that proxy.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203