{"document":{"category":"csaf_vex","csaf_version":"2.0","title":"CVE-2026-34183: Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler","publisher":{"category":"vendor","name":"HarborGuard Database","namespace":"https://database.harborguard.co"},"tracking":{"id":"CVE-2026-34183","status":"final","version":"1","initial_release_date":"2026-06-09T16:03:23.623Z","current_release_date":"2026-06-10T15:51:12.557Z","revision_history":[{"date":"2026-06-09T16:03:23.623Z","number":"1","summary":"Initial machine-readable export from HarborGuard."}]},"distribution":{"tlp":{"label":"WHITE"},"text":"Public CVE data; freely redistributable."},"notes":[{"category":"description","text":"Issue summary: Remote peer may exhaust heap memory of the QUIC\nserver or client by flooding it with packets containing PATH_CHALLENGE\nframes.\n\nImpact summary: A malicious remote peer can cause an unbounded\nmemory allocation which can lead to an abnormal termination of the\napplication acting as a QUIC client or server and a Denial of Service.\n\nA remote peer may exhaust heap memory by flooding the local\nQUIC stack with PATH_CHALLENGE frames. The local QUIC stack\nallocates a PATH_RESPONSE frame for every PATH_CHALLENGE it receives.\nThe allocated PATH_RESPONSE frame gets freed only when the remote\npeer acknowledges reception of the PATH_RESPONSE frame which will\nnot be done by a malicious peer.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by\nthis issue. The QUIC stack is outside of OpenSSL FIPS module\nboundary.","title":"CVE description"}],"references":[{"category":"self","summary":"CVE-2026-34183 on HarborGuard Database","url":"https://database.harborguard.co/cve/CVE-2026-34183"},{"category":"external","summary":"CVE Record","url":"https://www.cve.org/CVERecord?id=CVE-2026-34183"},{"category":"external","summary":"OpenSSL Advisory","url":"https://openssl-library.org/news/secadv/20260609.txt"},{"category":"external","summary":"4.0.1 git commit","url":"https://github.com/openssl/openssl/commit/fbaa83859c01ad64f497b757aaf51be7d05ed9eb"},{"category":"external","summary":"3.6.3 git commit","url":"https://github.com/openssl/openssl/commit/5b306efb0b3779dfdd0803b4afc9d08c91f11517"},{"category":"external","summary":"3.5.7 git commit","url":"https://github.com/openssl/openssl/commit/7d06955ebe0ecf8adfd4c1e92018586da47ef9ac"},{"category":"external","summary":"3.4.6 git commit","url":"https://github.com/openssl/openssl/commit/d2e9efbe4900a373227deb136e8665401404ffac"}]},"product_tree":{"branches":[{"category":"vendor","name":"OpenSSL","branches":[{"category":"product_name","name":"OpenSSL","branches":[{"category":"product_version_range","name":">=4.0.0 <4.0.1","product":{"name":"OpenSSL OpenSSL >=4.0.0 <4.0.1","product_id":"CSAFPID-1","product_identification_helper":{"cpe":"cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*"}}},{"category":"product_version_range","name":">=3.6.0 <3.6.3","product":{"name":"OpenSSL OpenSSL >=3.6.0 <3.6.3","product_id":"CSAFPID-2","product_identification_helper":{"cpe":"cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*"}}},{"category":"product_version_range","name":">=3.5.0 <3.5.7","product":{"name":"OpenSSL OpenSSL >=3.5.0 <3.5.7","product_id":"CSAFPID-3","product_identification_helper":{"cpe":"cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*"}}},{"category":"product_version_range","name":">=3.4.0 <3.4.6","product":{"name":"OpenSSL OpenSSL >=3.4.0 <3.4.6","product_id":"CSAFPID-4","product_identification_helper":{"cpe":"cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*"}}}]}]}]},"vulnerabilities":[{"cve":"CVE-2026-34183","title":"Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler","notes":[{"category":"description","text":"Issue summary: Remote peer may exhaust heap memory of the QUIC\nserver or client by flooding it with packets containing PATH_CHALLENGE\nframes.\n\nImpact summary: A malicious remote peer can cause an unbounded\nmemory allocation which can lead to an abnormal termination of the\napplication acting as a QUIC client or server and a Denial of Service.\n\nA remote peer may exhaust heap memory by flooding the local\nQUIC stack with PATH_CHALLENGE frames. The local QUIC stack\nallocates a PATH_RESPONSE frame for every PATH_CHALLENGE it receives.\nThe allocated PATH_RESPONSE frame gets freed only when the remote\npeer acknowledges reception of the PATH_RESPONSE frame which will\nnot be done by a malicious peer.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by\nthis issue. The QUIC stack is outside of OpenSSL FIPS module\nboundary.","title":"CVE description"}],"product_status":{"known_affected":["CSAFPID-1","CSAFPID-2","CSAFPID-3","CSAFPID-4"]},"scores":[{"cvss_v3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","baseScore":7.5,"baseSeverity":"HIGH"},"products":["CSAFPID-1","CSAFPID-2","CSAFPID-3","CSAFPID-4"]}],"remediations":[{"category":"vendor_fix","details":"Update to a fixed version: 3.4.6, 3.5.7, 3.6.3, 4.0.1.","product_ids":["CSAFPID-1","CSAFPID-2","CSAFPID-3","CSAFPID-4"],"url":"https://github.com/openssl/openssl/commit/fbaa83859c01ad64f497b757aaf51be7d05ed9eb"}]}]}