{"api_version":"1","generated_at":"2026-11-11T02:02:15+00:00","cve":"CVE-2026-95691","urls":{"html":"https://cve.report/CVE-2026-95691","api":"https://cve.report/api/cve/CVE-2026-95691.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-95691","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-95691"},"summary":{"title":"Retransmitted QUIC CRYPTO Frames Can Cause DoS or One-byte Disclosure","description":"Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage\nwhile the TLS record layer retains a direct pointer into that storage causing\nuse after free.\n\nImpact summary: A malicious QUIC server can cause a heap-use-after-free read\nin the OpenSSL QUIC client. The server can also identify one allocator-adjacent\nbyte through the client's protected Handshake response.\n\nCWE: CWE-416: Use After Free\n\nDescription: During CRYPTO stream processing, a pointer into the first frame's\nmemory on the stream is lent to the TLS handshake processing. The memory\nmust remain stable until it is processed and released. However the processing\nof retransmitted CRYPTO frames could release the memory if the retransmitted\nframe fully overlapped the existing frame. This then causes use-after-free read\nwhen the TLS handshake processing continues.\n\nThe use-after-free read can lead to a Denial-of-Service of the client\napplication or a minor leak of information about the heap memory contents\nthat might be overwritten with other data, subsequently allocated by\nthe application, to the peer.\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary.","state":"PUBLISHED","assigner":"openssl","published_at":"2026-11-10 19:21:39","updated_at":"2026-11-10 22:10:04"},"problem_types":["CWE-416","CWE-416 CWE-416 Use After Free"],"metrics":[],"references":[{"url":"https://github.com/openssl/openssl/commit/ec9d4de9d03989b29db5a3d7efdb4c285deaf386","name":"https://github.com/openssl/openssl/commit/ec9d4de9d03989b29db5a3d7efdb4c285deaf386","refsource":"openssl-security@openssl.org","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/openssl/openssl/commit/f6244675833e097c2429a40d1b206d95385bd42f","name":"https://github.com/openssl/openssl/commit/f6244675833e097c2429a40d1b206d95385bd42f","refsource":"openssl-security@openssl.org","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/openssl/openssl/commit/dd90ceb99a3c2ddba336bb4a00be9ebabd84c2a1","name":"https://github.com/openssl/openssl/commit/dd90ceb99a3c2ddba336bb4a00be9ebabd84c2a1","refsource":"openssl-security@openssl.org","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://openssl-library.org/news/secadv/20261110.txt","name":"https://openssl-library.org/news/secadv/20261110.txt","refsource":"openssl-security@openssl.org","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-95691","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-95691","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"OpenSSL","product":"OpenSSL","version":"affected 4.1.0 4.1.1 semver","platforms":[]},{"source":"CNA","vendor":"OpenSSL","product":"OpenSSL","version":"affected 4.0.0 4.0.4 semver","platforms":[]},{"source":"CNA","vendor":"OpenSSL","product":"OpenSSL","version":"affected 3.5.0 3.5.10 semver","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"Filipe Casal (Trail of Bits)","lang":"en"},{"source":"CNA","value":"Filipe Casal (Trail of Bits)","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"OpenSSL","vendor":"OpenSSL","versions":[{"lessThan":"4.1.1","status":"affected","version":"4.1.0","versionType":"semver"},{"lessThan":"4.0.4","status":"affected","version":"4.0.0","versionType":"semver"},{"lessThan":"3.5.10","status":"affected","version":"3.5.0","versionType":"semver"}]}],"credits":[{"lang":"en","type":"reporter","value":"Filipe Casal (Trail of Bits)"},{"lang":"en","type":"remediation developer","value":"Filipe Casal (Trail of Bits)"}],"datePublic":"2026-11-10T11:00:00.000Z","descriptions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage<br>while the TLS record layer retains a direct pointer into that storage causing<br>use after free.<br><br>Impact summary: A malicious QUIC server can cause a heap-use-after-free read<br>in the OpenSSL QUIC client. The server can also identify one allocator-adjacent<br>byte through the client's protected Handshake response.<br><br>CWE: CWE-416: Use After Free<br><br>Description: During CRYPTO stream processing, a pointer into the first frame's<br>memory on the stream is lent to the TLS handshake processing. The memory<br>must remain stable until it is processed and released. However the processing<br>of retransmitted CRYPTO frames could release the memory if the retransmitted<br>frame fully overlapped the existing frame. This then causes use-after-free read<br>when the TLS handshake processing continues.<br><br>The use-after-free read can lead to a Denial-of-Service of the client<br>application or a minor leak of information about the heap memory contents<br>that might be overwritten with other data, subsequently allocated by<br>the application, to the peer.<br><br>FIPS impact: no<br>The FIPS module is not affected as the QUIC implementation is outside of<br>the OpenSSL FIPS module boundary."}],"value":"Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage\nwhile the TLS record layer retains a direct pointer into that storage causing\nuse after free.\n\nImpact summary: A malicious QUIC server can cause a heap-use-after-free read\nin the OpenSSL QUIC client. The server can also identify one allocator-adjacent\nbyte through the client's protected Handshake response.\n\nCWE: CWE-416: Use After Free\n\nDescription: During CRYPTO stream processing, a pointer into the first frame's\nmemory on the stream is lent to the TLS handshake processing. The memory\nmust remain stable until it is processed and released. However the processing\nof retransmitted CRYPTO frames could release the memory if the retransmitted\nframe fully overlapped the existing frame. This then causes use-after-free read\nwhen the TLS handshake processing continues.\n\nThe use-after-free read can lead to a Denial-of-Service of the client\napplication or a minor leak of information about the heap memory contents\nthat might be overwritten with other data, subsequently allocated by\nthe application, to the peer.\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary."}],"metrics":[{"format":"other","other":{"content":{"text":"Low"},"type":"https://openssl-library.org/policies/general/security-policy/"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-416","description":"CWE-416 Use After Free","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-10T18:16:03.752Z","orgId":"3a12439a-ef3a-4c79-92e6-6081a721f1e5","shortName":"openssl"},"references":[{"name":"OpenSSL Advisory","tags":["vendor-advisory"],"url":"https://openssl-library.org/news/secadv/20261110.txt"},{"name":"4.1.1 git commit","tags":["patch"],"url":"https://github.com/openssl/openssl/commit/dd90ceb99a3c2ddba336bb4a00be9ebabd84c2a1"},{"name":"4.0.4 git commit","tags":["patch"],"url":"https://github.com/openssl/openssl/commit/ec9d4de9d03989b29db5a3d7efdb4c285deaf386"},{"name":"3.5.10 git commit","tags":["patch"],"url":"https://github.com/openssl/openssl/commit/f6244675833e097c2429a40d1b206d95385bd42f"}],"source":{"discovery":"UNKNOWN"},"title":"Retransmitted QUIC CRYPTO Frames Can Cause DoS or One-byte Disclosure","x_generator":{"engine":"Vulnogram 0.2.0"}}},"cveMetadata":{"assignerOrgId":"3a12439a-ef3a-4c79-92e6-6081a721f1e5","assignerShortName":"openssl","cveId":"CVE-2026-95691","datePublished":"2026-11-10T18:16:03.752Z","dateReserved":"2026-09-22T14:18:48.635Z","dateUpdated":"2026-11-10T18:16:03.752Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-10 19:21:39","lastModifiedDate":"2026-11-10 22:10:04","problem_types":["CWE-416","CWE-416 CWE-416 Use After Free"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"95691","Ordinal":"1","Title":"Retransmitted QUIC CRYPTO Frames Can Cause DoS or One-byte Discl","CVE":"CVE-2026-95691","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"95691","Ordinal":"1","NoteData":"Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage\nwhile the TLS record layer retains a direct pointer into that storage causing\nuse after free.\n\nImpact summary: A malicious QUIC server can cause a heap-use-after-free read\nin the OpenSSL QUIC client. The server can also identify one allocator-adjacent\nbyte through the client's protected Handshake response.\n\nCWE: CWE-416: Use After Free\n\nDescription: During CRYPTO stream processing, a pointer into the first frame's\nmemory on the stream is lent to the TLS handshake processing. The memory\nmust remain stable until it is processed and released. However the processing\nof retransmitted CRYPTO frames could release the memory if the retransmitted\nframe fully overlapped the existing frame. This then causes use-after-free read\nwhen the TLS handshake processing continues.\n\nThe use-after-free read can lead to a Denial-of-Service of the client\napplication or a minor leak of information about the heap memory contents\nthat might be overwritten with other data, subsequently allocated by\nthe application, to the peer.\n\nFIPS impact: no\nThe FIPS module is not affected as the QUIC implementation is outside of\nthe OpenSSL FIPS module boundary.","Type":"Description","Title":"Retransmitted QUIC CRYPTO Frames Can Cause DoS or One-byte Discl"}]}}}