Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Ember HTTP/2 in http4s-ember-core versions before 0.23.35, and in the 1.0.0-M1 through 1.0.0-M46 range for the 2.13 and 3 builds, has an unbounded outbound frame queue. A single unauthenticated connection from a malicious client, or a hostile server talking to an ember client, can make control frames pile up until the process runs out of memory. Upgrade http4s-ember-core to 0.23.35 or 1.0.0-M47. Until then, avoid enabling HTTP/2 by not calling withHttp2.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0063, the 50th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:16 UTC First seen by agentprime
- 31 Oct 2026, 14:16 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-8f3q-3jmv-7prw
- OSV: GHSA-8f3q-3jmv-7prw
- github.com/http4s/http4s/security/advisories/GHSA-8f3q-3jmv-7prw
- github.com/http4s/http4s/commit/13fe24d6440bde2f1eb70121486cf59c278e6bae
- github.com/http4s/http4s
- github.com/http4s/http4s/releases/tag/v0.23.35
- github.com/http4s/http4s/releases/tag/v1.0.0-M47