Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.7
OpenSSL QUIC server can amplify DDoS traffic
published 2 days ago
Summary
When the OpenSSL QUIC server is set to skip address validation, it can be tricked into counting the same incoming data multiple times. This lets a remote attacker cause the server to send up to three times more data than it receives, enabling amplified denial‑of‑service attacks. Keep address validation enabled or upgrade to a version of OpenSSL that corrects this behavior.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Docker Hardened Images:Debian:13 | docker hardened images | openssl | All versions |
Original advisory text
Issue summary: The OpenSSL QUIC server, when configured to not preform address
Issue summary: The OpenSSL QUIC server, when configured to not preform address
validation, can be forced to count incoming packets multiple times in its
unvalidated credit computation, leading to a violation of the RFC 9000
unvalidated connection amplification limit of 3 times the amount of data
received.
Impact summary: A remote attacker able to spoof packets to a server using the
OpenSSL QUIC implementation might use the server for an amplification of
a DDoS attack.
CWE: CWE-440: Expected Behavior Violation
Description: OpenSSL's QUIC stack, when operating as a server, enforces client
address validation (RFC 9000, Section 8), to confirm the peer address is not
used for a traffic amplification attack. If this feature is disabled on the
server, the QUIC stack limits the amount of server data that can be sent to 3
times the amount of data received from the peer address, until such time as the
TLS handshake is completed.
The OpenSSL QUIC server, when operating in non-validation mode, adds the
length of the whole datagram received to the unvalidated credit limit when
processing each QUIC packet in the datagram. A remote peer may,
after establishing a connection with an initial client hello frame, send a
subsequent datagram containing multiple QUIC packets, leading the server to
account the entire datagram length for each packet in the datagram, resulting
in the server believing that the peer has sent more data than it actually has,
thereby violating the 3x amplification limit mandated by the RFC.
FIPS impact: no
As the QUIC stack lives outside the FIPS module boundary, no FIPS modules
are affected by this CVE.
validation, can be forced to count incoming packets multiple times in its
unvalidated credit computation, leading to a violation of the RFC 9000
unvalidated connection amplification limit of 3 times the amount of data
received.
Impact summary: A remote attacker able to spoof packets to a server using the
OpenSSL QUIC implementation might use the server for an amplification of
a DDoS attack.
CWE: CWE-440: Expected Behavior Violation
Description: OpenSSL's QUIC stack, when operating as a server, enforces client
address validation (RFC 9000, Section 8), to confirm the peer address is not
used for a traffic amplification attack. If this feature is disabled on the
server, the QUIC stack limits the amount of server data that can be sent to 3
times the amount of data received from the peer address, until such time as the
TLS handshake is completed.
The OpenSSL QUIC server, when operating in non-validation mode, adds the
length of the whole datagram received to the unvalidated credit limit when
processing each QUIC packet in the datagram. A remote peer may,
after establishing a connection with an initial client hello frame, send a
subsequent datagram containing multiple QUIC packets, leading the server to
account the entire datagram length for each packet in the datagram, resulting
in the server believing that the peer has sent more data than it actually has,
thereby violating the 3x amplification limit mandated by the RFC.
FIPS impact: no
As the QUIC stack lives outside the FIPS module boundary, no FIPS modules
are affected by this CVE.
References
- https://scout.docker.com/v/DHI-rcd3-gm2j-br4x-dy42 Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-35191 Vendor Advisory
- https://openssl-library.org/news/secadv/20260929.txt Vendor Advisory
- https://github.com/openssl/openssl/commit/e44292e58b090014232ef75bd400393851b24d... Patch
- https://github.com/openssl/openssl/commit/2de4c35fb13fc58f43fd8dc1d261700472ce72... Patch
- https://github.com/openssl/openssl/commit/0fe4442d4f8ea3af8a174046dae176e0d47172... Patch
- https://errata.almalinux.org/9/ALSA-2026-98484.html Vendor Advisory
- https://access.redhat.com/errata/RHSA-2026:98484 Vendor Advisory
- https://alas.aws.amazon.com/AL2023/ALAS-2026-3204.html Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-84784 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-84782 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-75806 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-75805 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-75804 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-72897 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-54873 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-54872 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42772 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-35191 Vendor Advisory
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-35189 Vendor Advisory
- https://security-tracker.debian.org/tracker/CVE-2026-35191 Vendor Advisory
- https://linux.oracle.com/cve/ELSA-2026-98484.html Vendor Advisory
- https://linux.oracle.com/errata/ELSA-2026-98484.html Vendor Advisory
- https://access.redhat.com/security/cve/CVE-2026-35191 Vendor Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-35191 Patch
- https://errata.rockylinux.org/RLSA-2026:98484 Vendor Advisory
- https://errata.rockylinux.org/RLSA-2026:98588 Vendor Advisory
- https://ubuntu.com/security/CVE-2026-35191 Vendor Advisory
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-35191 Vendor Advisory
Internet-facing
14 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically (estimated)
- Gives an attacker partial control (estimated)
Timeline
Published20 Nov 2026
Updated20 Nov 2026
First seen20 Nov 2026
Sources
DHI-rcd3-gm2j-br4x-dy42 · OSV
Track software like this
Free during beta