{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44452 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44452 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44452 is a medium-severity memory corruption vulnerability in h2o, 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-44452 and fix it if it is affected.\n\nWhat it is: CVE-2026-44452 is a medium-severity memory corruption vulnerability in h2o, 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-44452 in the wild and no public exploit code.\n\nAffected product: h2o. 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-44452/ (Markdown: https://insights.sbomify.com/CVE-2026-44452/index.md)","id":"CVE-2026-44452","markdown":"https://insights.sbomify.com/CVE-2026-44452/index.md","name":"CVE-2026-44452","record":{"aliases":["DEBIAN-CVE-2026-44452","GHSA-w68q-rqwx-7wvq","UBUNTU-CVE-2026-44452"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"h2o HTTP server","requires_auth":"none","summary":"An attacker can cause a denial of service in the h2o HTTP server by sending a TLS or QUIC ClientHello with a zero-length SNI extension, triggering a heap overrun.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"h2o","vendor":"h2o"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-170","name":"Improper Null Termination"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. Prior to commit 8dc37cb, when h2o receives a ClientHello message over TLS or QUIC and it contains a zero-length SNI extension, the h2o server runs over the zero-length hostname while trying to copy the hostname, assuming that it is NULL-terminated. This is a potential denial-of-service attack vector in sense that it might trigger segmentation violation. This issue has been fixed by commit 8dc37cb.","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":"h2o is vulnerable to heap overrun","id":"CVE-2026-44452","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"h2o is vulnerable to musl libc stack overflow","id":"CVE-2026-44453"},"packages":[],"prev":{"headline":"Lumiverse: TSX component sandbox escape via DOM ref and string-split identifier bypass","id":"CVE-2026-44451"},"products":["h2o"],"published":"2026-07-16","related":[{"cvss_score":10,"headline":"H2O Remote Code Execution via POJO Model Import","id":"CVE-2023-6016","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":9.8,"headline":"Deserialization Vulnerability in h2oai/h2o-3","id":"CVE-2025-6544","kev_date_added":null,"published":"2025-09-21"},{"cvss_score":9.8,"headline":"Jdbc Deserialization in h2oai/h2o-3","id":"CVE-2024-10553","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":9.3,"headline":"External Control of File Name or Path in h2oai/h2o-3","id":"CVE-2023-6569","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":9.3,"headline":"H2O Local File Include","id":"CVE-2023-6013","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":9.3,"headline":"Local File Inclusion in h2oai/h2o-3","id":"CVE-2023-6038","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":9.1,"headline":"H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL","id":"CVE-2024-45758","kev_date_added":null,"published":"2024-09-06"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-17","vendors":["h2o"]},"summary":"An attacker can cause a denial of service in the h2o HTTP server by sending a TLS or QUIC ClientHello with a zero-length SNI extension, triggering a heap overrun.","url":"https://insights.sbomify.com/CVE-2026-44452/"}