Loading
Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: <= 0.23.34
Patched in 0.23.35
Vulnerable: <= 0.23.34
Patched in 0.23.35
Vulnerable: <= 0.23.34
Patched in 0.23.35
Vulnerable: >= 1.0.0-M1, <= 1.0.0-M46
Patched in 1.0.0-M47
Vulnerable: >= 1.0.0-M1, <= 1.0.0-M46
Patched in 1.0.0-M47
Details
An ember server with HTTP/2 enabled (.withHttp2) does not enforce SETTINGS_MAX_CONCURRENT_STREAMS on streams opened by the peer. A single unauthenticated connection can open an unbounded number of concurrent streams, each of which allocates per-stream server state that is never released, exhausting the heap.
Unauthenticated remote denial of service (memory exhaustion) against any Ember server built .withHttp2. This is the resource-exhaustion class of the HTTP/2 "Rapid Reset" family (CVE-2023-44487).
The same unchecked allocation path is reachable on the client via server-initiated PUSH_PROMISE frames, so a malicious or compromised server can exhaust an ember-client's heap the same way.
.withHttp2 enabled.enablePush is not enforced.EmberServerBuilder or EmberClientBuilder (default)EPSS, exploit probability
Low0.63%
estimated chance of real-world exploitation in the next 30 days, higher than 50.1% of every CVE FIRST.org scores
Refreshed 10/31/2026, via FIRST.org's EPSS model, not CVSS, this measures likelihood of exploitation, not how severe it would be.
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.