{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-45271 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-45271 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-45271 is a medium-severity denial of service vulnerability in h2o picotls, published on 21 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-45271 and fix it if it is affected.\n\nWhat it is: CVE-2026-45271 is a medium-severity denial of service vulnerability in h2o picotls, published on 21 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-45271 in the wild and no public exploit code.\n\nAffected product: h2o picotls. 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-45271/ (Markdown: https://insights.sbomify.com/CVE-2026-45271/index.md)","id":"CVE-2026-45271","markdown":"https://insights.sbomify.com/CVE-2026-45271/index.md","name":"CVE-2026-45271","record":{"aliases":["GHSA-84f5-m5x2-82q4"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TLS protocol library","requires_auth":"none","summary":"An attacker can crash applications using the minicrypto backend by supplying a deeply nested ASN.1 structure in a private key file.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-835","name":"Loop with Unreachable Exit Condition"}],"description":"Picotls is a TLS protocol library that allows users select different crypto backends based on their use case. Picotls implements its own ASN.1 validation helper, which is used by the minicrypto backend while parsing local PKCS#8 private keys. Prior to commit c14231d801407640bc42c2dcf92783409ea6a7c7, the validator recursively descends into constructed ASN.1 elements without enforcing a maximum nesting depth. If an application loads an attacker-supplied private-key file through ptls_minicrypto_load_private_key(), or otherwise calls the public ASN.1 validation API on untrusted DER, a crafted deeply nested ASN.1 structure can exhaust the process stack and crash the application. Note that the libcrypto (OpenSSL) backend does not use the ASN.1 validation helper of picotls, and therefore is immune to this vulnerability. The vulnerability has been addressed in commit c14231d801407640bc42c2dcf92783409ea6a7c7.","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":"picotls has infinite recursion in the minicrypto ASN.1 decoder","id":"CVE-2026-45271","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":"MyBooks: Remote Code Execution via SOCIAL_AUTH Key Name Injection in Python Config File","id":"CVE-2026-45272"},"packages":[],"prev":{"headline":"CI4MS: Stored XSS in Pages Module Content via Broken html_purify Validation Rule","id":"CVE-2026-45270"},"products":["picotls"],"published":"2026-08-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-08-25","vendors":["h2o"]},"summary":"An attacker can crash applications using the minicrypto backend by supplying a deeply nested ASN.1 structure in a private key file.","url":"https://insights.sbomify.com/CVE-2026-45271/"}