# CVE-2026-48615: Information disclosure in node

> Attackers can expose proxy credentials via error messages in Node.js, potentially leading to credential theft if logs are accessible.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** ALPINE-CVE-2026-48615, AZL-91230, BELL-CVE-2026-48615, BIT-node-2026-48615, BIT-node-min-2026-48615, DEBIAN-CVE-2026-48615, ECHO-117a-9a28-6844, GHSA-qqjm-7pv6-7q82, MINI-3wcr-h7r6-9p79, MINI-fmcj-wq7p-p234, MINI-w36v-qqj8-cc6v, UBUNTU-CVE-2026-48615

## What is CVE-2026-48615?

CVE-2026-48615 is a medium-severity vulnerability in Nodejs Node.js, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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**.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-48615?

2 open source packages ship an affected version, including node and node-min. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | From 22.22.3 | 22.23.0, 24.17.0, 26.3.1 |
| `node-min` | Bitnami | From 22.22.3 | 22.23.0, 24.17.0, 26.3.1 |

Products: Nodejs Node.js.

## How do I fix CVE-2026-48615?

Upgrade node to a fixed version for your release line: 22.23.0, 24.17.0 or 26.3.1.

## Is CVE-2026-48615 being exploited?

There is no known exploitation of CVE-2026-48615 in the wild and no public exploit code.

## Other vulnerabilities in Nodejs Node.js

- [CVE-2023-32002](https://insights.sbomify.com/CVE-2023-32002/): Security feature bypass in Node (critical 9.8)
- [CVE-2016-6303](https://insights.sbomify.com/CVE-2016-6303/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-15896](https://insights.sbomify.com/CVE-2017-15896/): Security feature bypass in Node.js (critical 9.1)
- [CVE-2018-7160](https://insights.sbomify.com/CVE-2018-7160/): Server-side request forgery in Node.js (high 8.8)
- [CVE-2018-12120](https://insights.sbomify.com/CVE-2018-12120/): Misconfiguration in Node.js (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48615 and fix it if it is affected.

What it is: CVE-2026-48615 is a medium-severity vulnerability in Nodejs Node.js, published on 26 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48615 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected from 22.22.3; fixed in 22.23.0, 24.17.0, 26.3.1
- node-min (Bitnami): affected from 22.22.3; fixed in 22.23.0, 24.17.0, 26.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48615/ (Markdown: https://insights.sbomify.com/CVE-2026-48615/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48615
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48615
- OSV: https://osv.dev/vulnerability/CVE-2026-48615

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48615/
Summaries are generated and may contain mistakes; the official description above is the record.