{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44435 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44435 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44435 is a high-severity denial of service vulnerability in h2o quicly, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44435 and fix it if it is affected.\n\nWhat it is: CVE-2026-44435 is a high-severity denial of service vulnerability in h2o quicly, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-44435 in the wild and no public exploit code.\n\nAffected product: h2o quicly. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44435/ (Markdown: https://insights.sbomify.com/CVE-2026-44435/index.md)","id":"CVE-2026-44435","markdown":"https://insights.sbomify.com/CVE-2026-44435/index.md","name":"CVE-2026-44435","record":{"aliases":["GHSA-2cw9-5673-73gv"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"QUIC protocol library","requires_auth":"none","summary":"Remote attackers can cause a denial of service in Quicly by sending handshake data exceeding 32KB, triggering an assertion failure.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"quicly","vendor":"h2o"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit 937d0e9, an assertion failure is raised when the total number of valid handshake messages received over a CRYPTO stream of a single packet number space exceeds 32KB, causing a Denial of Service. This issue has been fixed by commit 937d0e9.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Quicly: Remote Denial of Service via assertion failure when CRYPTO stream handshake data exceeds 32KB","id":"CVE-2026-44435","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Quicly is vulnerable to connection state corruption","id":"CVE-2026-44436"},"packages":[],"prev":{"headline":"Quicly is vulnerable to stateless reset injection","id":"CVE-2026-44434"},"products":["quicly"],"published":"2026-07-16","related":[{"cvss_score":7.5,"headline":"Quicly is vulnerable to connection state corruption","id":"CVE-2026-44436","kev_date_added":null,"published":"2026-07-16"},{"cvss_score":7.5,"headline":"Quicly has assertion failures","id":"CVE-2025-61684","kev_date_added":null,"published":"2026-01-19"},{"cvss_score":5.3,"headline":"Quicly is vulnerable to memory exhaustion","id":"CVE-2026-44433","kev_date_added":null,"published":"2026-07-16"},{"cvss_score":5.3,"headline":"Quicly is vulnerable to stateless reset injection","id":"CVE-2026-44434","kev_date_added":null,"published":"2026-07-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-17","vendors":["h2o"]},"summary":"Remote attackers can cause a denial of service in Quicly by sending handshake data exceeding 32KB, triggering an assertion failure.","url":"https://insights.sbomify.com/CVE-2026-44435/"}