ALPINE-CVE-2026-123866: Use After Free

Published Nov 11, 2026
·
Updated

A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections' response buffers, to a peer. When a stream is torn down while a write is still backpressured, for example by a peer RSTSTREAM or by the server's own per-stream timeout destroying the stream, the stream's response buffer is freed but a reference to it is still used, so freed or unrelated heap memory is written to the socket instead of the intended response. On Node.js 26.x and 24.x the teardown can be driven purely by a remote peer once the window-size change from 26.9.0 and 24.22.0 is present, and on all supported lines the same defect is reachable through an application-initiated teardown such as a per-stream idle timeout. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Affected Software

4 affected componentsFixes available
alpine/nodejs<22.23.5-r0
22.23.5-r0
alpine/nodejs<22.23.5-r0
22.23.5-r0
alpine/nodejs<24.22.3-r0
24.22.3-r0
alpine/nodejs<24.22.3-r0
24.22.3-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade alpine/nodejs to a version that resolves this vulnerability.

    Fixed in 22.23.5-r0
  2. Upgrade

    Upgrade alpine/nodejs to a version that resolves this vulnerability.

    Fixed in 24.22.3-r0

Event History

Nov 11, 2026
CVE Published
via OSV·07:17 PM
Data Sourced
via OSV·07:17 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which Node.js deployments are exposed?

The issue affects Node.js 26.x, 24.x, and 22.x when HTTP/2 streams can be torn down while a response write remains backpressured. The affected Alpine package is alpine/nodejs.

2

Can an unauthenticated remote peer trigger the issue?

On Node.js 26.x and 24.x, a remote peer can drive the teardown after the window-size change present in 26.9.0 and 24.22.0, such as by sending RST_STREAM. On all supported lines, exploitation is also reachable when the application itself destroys a stream, including through a per-stream idle timeout.

3

What is the likely impact of successful exploitation?

A peer may receive freed or unrelated heap memory in place of the intended response. This can disclose response-buffer contents associated with other connections; the provided severity vector indicates confidentiality impact without stated integrity or availability impact.

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