<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-16T18:27:00.062431+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/euvd-2026-367115</id>
    <title>EUVD-2026-367115</title>
    <updated>2026-11-16T18:27:00.085531+00:00</updated>
    <content>EUVD-2026-367115</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-367115"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-88012</id>
    <title>fkie_cve-2026-88012</title>
    <updated>2026-11-16T18:27:00.085569+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Traefik is an open source HTTP reverse proxy and load balancer. From 2.8.2 until 2.11.56 and 3.7.12, HTTP/3 entrypoints do not apply entryPoints..transport.respondingTimeouts.readTimeout because the timeout is enforced on a TCP connection and the HTTP/3 server has no corresponding QUIC stream deadline. An unauthenticated client can use a slow request body, trickling data indefinitely while holding a request and an upstream connection open and exhausting backends with bounded connection pools. This issue is fixed in 2.11.56 and 3.7.12.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-88012"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-7ghq-v6jf-g56c</id>
    <title>GHSA-7ghq-v6jf-g56c — Traefik: respondingTimeouts.readTimeout is not applied to HTTP/3, leaving slow-body uploads unbounded</title>
    <updated>2026-11-16T18:27:00.085606+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/traefik/traefik/v2, Go: github.com/traefik/traefik/v3</p>
<p>## Summary</p>
<p>There is a medium severity vulnerability in Traefik's HTTP/3 entry points: the `respondingTimeouts` settings were not applied to the HTTP/3 request path. `readTimeout` in particular is on by default at 60s and is documented as bounding the time to read the entire request including its body, but it is enforced as a deadline on the TCP connection, which cannot reach a QUIC stream, and Traefik's HTTP/3 server was constructed with no timeout of any kind. An unauthenticated client that trickles a request body therefore holds a request open for as long as it chooses, and with it one upstream connection per request, at negligible cost to itself. Backends with bounded connection pools are the practical pressure point.</p>
<p>The HTTP/3 path lost these timeouts in v2.8.2, when a quic-go API change removed the embedded `http.Server` that had carried them; every release from v2.8.2 onward is affected, and releases before v2.8.2 are not. Traefik v2.8.2 through v2.10.x and v3.0 through v3.6 are affected and are no longer maintained: they will not receive a patch on their own line, and the remedy for their users is to upgrade to v2.11.56 or v3.7.12.</p>
<p>## Patches</p>
<p>- https://github.com/traefik/traefik/releases/tag/v2.11.56
- https://github.com/traefik/traefik/releases/tag/v3.7.12</p>
<p>## For more information</p>
<p>If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).</p>
<p>&lt;details&gt;
&lt;summary&gt;Original Description&lt;/summary&gt;</p>
<p>## Su…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-7ghq-v6jf-g56c"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:90321</id>
    <title>RHSA-2026:90321 — Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.31.0 Release.</title>
    <updated>2026-11-16T18:27:00.085703+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>axios: Axios: Server-Side Request Forgery and proxy bypass due to improper hostname normalization python-pip: Path traversal via malicious entry point name in pip wheel installation allows arbitrary file overwrite pacote: Pacote: Denial of Service via crafted spec.rawSpec value in addGitSha function bouncycastle: Bouncy Castle: Denial of Service via untrusted keystore length allocation undici: undici: Information disclosure and Denial of Service via malformed Cache-Control directives org.bouncycastle/bcprov-jdk15on: org.bouncycastle/bcprov-jdk18on: org.bouncycastle/bc-fips: org.bouncycastle/bctls-fips: Bouncy Castle for Java: Denial of Service due to unbounded memory allocation io.vertx/vertx-web: Eclipse Vert.x Web Client: Information disclosure via improper cookie domain validation io.quarkus/quarkus-rest: io.quarkus/quarkus-vertx-http: io.quarkus.resteasy.reactive/resteasy-reactive: Quarkus REST - Unbounded multipart MIME part-header accumulation allows remote OOM denial of service github.com/moby/go-archive: moby/go-archive: Arbitrary file write via link following in tar extraction @fastify/static: @fastify/static: Information disclosure via route guard bypass org.eclipse.jetty/jetty-http: Jetty: HTTP request smuggling via crafted chunked requests undici: undici: Denial of Service via unrequested WebSocket subprotocol net/mail: golang: Go net/mail: Denial of Service via crafted email inputs github.com/open-telemetry/opentelemetry-go: go.opentelemetry.io/otel/baggage: go.…</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:90321"/>
  </entry>
</feed>
