ALPINE-CVE-2026-123871: Medium severity alpine/nodejs vulnerability
Node.js discloses proxy credentials in ERRPROXYINVALIDCONFIG error messages. CVE-2026-48615 established that a proxy credential must not appear in a Node.js error message and redacted the username and password from ProxyConfig.href, but that fix missed four error paths in the same subsystem, one of them inside the same constructor, which interpolate the raw proxy URL, credentials included, into an ERRPROXYINVALIDCONFIG message. The proxy URL comes from the environment, but the defect is the sink: a secret that Node.js redacts everywhere else is emitted verbatim into a much wider audience than the process environment, such as stderr, container logs, log aggregation, and crash reporting services. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/nodejsto a version that resolves this vulnerability.Fixed in 22.23.5-r0 - Upgrade
Upgrade
alpine/nodejsto a version that resolves this vulnerability.Fixed in 24.22.3-r0
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments running Node.js 22.x, 24.x, or 26.x are affected when a proxy URL containing credentials is supplied through the environment and reaches one of the unredacted invalid-configuration error paths.
How can I check for credential exposure?
Search stderr, container logs, centralized log aggregation, and crash-reporting records for ERR_PROXY_INVALID_CONFIG messages. Review any matching messages for proxy URLs that include usernames or passwords.
What can be done if updating is not immediately possible?
Avoid supplying proxy credentials in proxy URLs through the environment where possible. Treat logs and crash-reporting data that may contain ERR_PROXY_INVALID_CONFIG output as potentially containing exposed proxy credentials and restrict access accordingly.