{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-19201 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-19201 is a medium-severity denial of service vulnerability in Google go-attestation, published on 8 Sep 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-19201 and fix it if it is affected.\n\nWhat it is: CVE-2026-19201 is a medium-severity denial of service vulnerability in Google go-attestation, published on 8 Sep 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-19201 in the wild and no public exploit code.\n\nAffected product: Google go-attestation. 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-19201/ (Markdown: https://insights.sbomify.com/CVE-2026-19201/index.md)","id":"CVE-2026-19201","markdown":"https://insights.sbomify.com/CVE-2026-19201/index.md","name":"CVE-2026-19201","record":{"aliases":["DEBIAN-CVE-2026-19201","GHSA-7rqw-p8mv-672c","GHSA-hcm6-rjfh-f25p","UBUNTU-CVE-2026-19201"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Go attestation library","requires_auth":"none","summary":"An attacker can crash the verifier application by submitting a crafted Windows event log with deeply nested headers, causing a stack overflow.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"go-attestation","vendor":"google"}],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-674","name":"Uncontrolled Recursion"}],"description":"An uncontrolled recursion vulnerability in the Windows SIPA event log parser of Google go-attestation versions up to and including 0.6.1 allows an attacker to cause a denial of service (DoS). The (*WinEvents).readELAMAggregation function recurses for every nested elamAggregation sub-event without enforcing a maximum recursion depth limit, while the size guard is bypassed on recursive execution paths. By submitting a crafted Windows event log containing deeply nested elamAggregation headers, an attacker can exhaust the goroutine call stack, triggering an unrecoverable fatal runtime error (stack overflow) that immediately crashes the verifier application.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Denial of Service via Unbounded Recursion in go-attestation Windows SIPA Parser","id":"CVE-2026-19201","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Token Cache Reuse in mcp-toolbox-sdk-python","id":"CVE-2026-19202"},"packages":[],"prev":{"headline":"Velociraptor Analyst overwrites live built-in artifacts through verify()","id":"CVE-2026-19200"},"products":["go-attestation"],"published":"2026-09-08","related":[{"cvss_score":4,"headline":"Improper Input Validation in AKPublic.Verify in go-attestation","id":"CVE-2022-0317","kev_date_added":null,"published":"2022-02-04"}],"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-09-10","vendors":["Google"]},"summary":"An attacker can crash the verifier application by submitting a crafted Windows event log with deeply nested headers, causing a stack overflow.","url":"https://insights.sbomify.com/CVE-2026-19201/"}