{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69186 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-69186 is a medium-severity denial of service vulnerability in c-ares, published on 18 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-69186 and fix it if it is affected.\n\nWhat it is: CVE-2026-69186 is a medium-severity denial of service vulnerability in c-ares, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69186 exists.\n\nAffected product: c-ares. 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-69186/ (Markdown: https://insights.sbomify.com/CVE-2026-69186/index.md)","id":"CVE-2026-69186","markdown":"https://insights.sbomify.com/CVE-2026-69186/index.md","name":"CVE-2026-69186","record":{"aliases":["AZL-103304","AZL-103454","BELL-CVE-2026-69186","DEBIAN-CVE-2026-69186","ECHO-9e60-294a-7216","GHSA-jv8r-gqr9-68wj","MINI-vfrm-8j62-rm2w","UBUNTU-CVE-2026-69186"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"c-ares DNS resolver","requires_auth":"none","summary":"A malicious DNS response can trigger excessive memory allocation in c-ares, leading to denial of service for applications using the library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"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-400","name":"Uncontrolled Resource Consumption"}],"description":"c-ares is an asynchronous resolver library. Prior to 1.34.7, ares_dns_parse() trusts the attacker-controlled ANCOUNT, NSCOUNT, and ARCOUNT fields before confirming that the DNS response contains enough bytes for the claimed records. Because process_answer() invokes parsing before transaction ID and question validation, a malicious DNS response can cause ares_dns_record_rr_prealloc() and ares_array_set_size() to reserve disproportionate heap memory for a tiny message. Repeated responses create large allocation and release cycles that can degrade or deny name resolution, without causing memory corruption or information disclosure. This issue is fixed in version 1.34.7.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"c-ares: Memory-amplification denial of service via unvalidated DNS header record counts","id":"CVE-2026-69186","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Hoppscotch: Cross-user private data exposure and UserHistory IDOR via team GraphQL resolvers","id":"CVE-2026-69189"},"packages":[],"prev":{"headline":"Socket.IO: Zero-attachment Memory Exhaustion","id":"CVE-2026-69185"},"products":["c-ares"],"published":"2026-09-18","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-18","vendors":["c-ares"]},"summary":"A malicious DNS response can trigger excessive memory allocation in c-ares, leading to denial of service for applications using the library.","url":"https://insights.sbomify.com/CVE-2026-69186/"}