<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T03:16:40.375016+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-69203</id>
    <title>fkie_cve-2026-69203</title>
    <updated>2026-09-30T03:16:40.393009+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Http4s is a Scala interface for HTTP services. Prior to 0.23.35 and 1.0.0-M47, An Ember server with HTTP/2 enabled through withHttp2 does not enforce SETTINGS_MAX_CONCURRENT_STREAMS for peer-created streams. One unauthenticated connection can open an unbounded number of streams, each retaining per-stream state until heap exhaustion. The same unchecked allocation is reachable in an ember-client through server-initiated PUSH_PROMISE frames because enablePush is not enforced. This issue is fixed in versions 0.23.35 and 1.0.0-M47.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-69203"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-9vwc-pc8p-253q</id>
    <title>GHSA-9vwc-pc8p-253q — Http4s Ember HTTP/2 does not enforce SETTINGS_MAX_CONCURRENT_STREAMS</title>
    <updated>2026-09-30T03:16:40.393089+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.http4s:http4s-ember-core_2.12, Maven: org.http4s:http4s-ember-core_2.13, Maven: org.http4s:http4s-ember-core_3</p>
<p>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.</p>
<p>## Impact</p>
<p>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).</p>
<p>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.</p>
<p>## Preconditions</p>
<p>- Server: with `.withHttp2` enabled.
- Client: makes HTTP/2 requests to malicious or compromised sites.  `enablePush` is not enforced.</p>
<p>## Workarounds</p>
<p>- Disable HTTP/2 on `EmberServerBuilder` or `EmberClientBuilder` (default)
- Client only: avoid HTTP/2 to untrusted servers until patched.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-9vwc-pc8p-253q"/>
  </entry>
</feed>
