# CVE-2026-48937: A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` frame.


- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** ALPINE-CVE-2026-48937, AZL-91127, BELL-CVE-2026-48937, BIT-node-2026-48937, BIT-node-min-2026-48937, DEBIAN-CVE-2026-48937, ECHO-9ee0-9b0a-f95f, GHSA-p9qf-hwxr-qhff, MINI-429h-7wh5-2wqh, MINI-c65q-99q4-24hg, MINI-fc8r-pf4m-5r98, MINI-fjfp-j966-p9gq, MINI-g978-34qj-cj2q, MINI-w7rh-w2vh-5gjf, UBUNTU-CVE-2026-48937

## What is CVE-2026-48937?

CVE-2026-48937 is a medium-severity vulnerability in Nodejs Node.js, published on 18 Jun 2026. 

### Official description

A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` frame. This vulnerability affects two supported release lines: **Node.js 22** and **Node.js 24**.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | All versions | 22.23.0, 24.17.0 |
| `node-min` | Bitnami | All versions | 22.23.0, 24.17.0 |

Products: Nodejs Node.js.

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

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

## Is CVE-2026-48937 being exploited?

There is no known exploitation of CVE-2026-48937 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-48937 and fix it if it is affected.

What it is: CVE-2026-48937 is a medium-severity vulnerability in Nodejs Node.js, published on 18 Jun 2026. 
Exploitation: There is no known exploitation of CVE-2026-48937 in the wild and no public exploit code.

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

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-48937/ (Markdown: https://insights.sbomify.com/CVE-2026-48937/index.md)
```

## Sources

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

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