{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44434 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44434 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44434 is a medium-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-44434 and fix it if it is affected.\n\nWhat it is: CVE-2026-44434 is a medium-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-44434 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-44434/ (Markdown: https://insights.sbomify.com/CVE-2026-44434/index.md)","id":"CVE-2026-44434","markdown":"https://insights.sbomify.com/CVE-2026-44434/index.md","name":"CVE-2026-44434","record":{"aliases":["GHSA-899f-49jq-pfh8"],"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":"An on-path attacker can terminate QUIC connections by injecting stateless resets due to improper validation of secret patterns in the Quicly library.","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":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-665","name":"Improper Initialization"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit dccf5d4, Quicly was vulnerable to stateless reset injection through lack of packet entry validation. The QUIC protocol is designed to withstand packet injection attacks, once the handshake is complete. Only packets that carry some secret patterns are considered as stateless resets. Quicly allows the peer to share up to 4 such patterns per connection. However, until now, it failed to determine which of the 4 slots that it uses to retain the secret patterns contains a valid entry. As the slots are zero-initialized, the failure meant that, unless the peer advertised 4 of such patterns, an all-zero pattern was treated as a stateless reset.In effect, this allowed an on-path attacker to reset QUIC connections governed by Quicly. This issue has been fixed by commit dccf5d4.","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 is vulnerable to stateless reset injection","id":"CVE-2026-44434","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: Remote Denial of Service via assertion failure when CRYPTO stream handshake data exceeds 32KB","id":"CVE-2026-44435"},"packages":[],"prev":{"headline":"Quicly is vulnerable to memory exhaustion","id":"CVE-2026-44433"},"products":["quicly"],"published":"2026-07-16","related":[{"cvss_score":7.5,"headline":"Quicly: Remote Denial of Service via assertion failure when CRYPTO stream handshake data exceeds 32KB","id":"CVE-2026-44435","kev_date_added":null,"published":"2026-07-16"},{"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"}],"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-18","vendors":["h2o"]},"summary":"An on-path attacker can terminate QUIC connections by injecting stateless resets due to improper validation of secret patterns in the Quicly library.","url":"https://insights.sbomify.com/CVE-2026-44434/"}