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.
CVE-2026-69186
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-83212 (ENISA EUVD)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMmedium confidence
- EG Risk
- 55EG Risk 55/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.5%
- EPSS %ILE
- 40th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 18, 2026
Last Modified
September 23, 2026
Advisory Details (5)
Auto-updated Sep 18, 20261.34.7
Patch available: c-ares/c-ares v1.34.7
https://github.com/c-ares/c-ares/releases/tag/v1.34.7commit eaded4cb200b (c-ares/c-ares)
Fix landed in c-ares/c-ares commit eaded4cb200b — awaiting tagged release
https://github.com/c-ares/c-ares/commit/eaded4cb200b2a5f8d73f11021ff7c8d6968aaabcommit e47c203f91cd (c-ares/c-ares)
Patch available: c-ares/c-ares v1.34.7 (contains commit e47c203f91cd)
https://github.com/c-ares/c-ares/commit/e47c203f91cd8b749c8736bc18d75a31ffdec8f4validate RR counts before preallocation to reject malformed packets early
Fix merged in c-ares/c-ares PR #1134 on 2026-04-12 — awaiting tagged release
https://github.com/c-ares/c-ares/pull/1134Memory-amplification denial of service via unvalidated DNS header record counts · Advisory · c-ares/c-ares · GitHub
https://github.com/c-ares/c-ares/security/advisories/GHSA-jv8r-gqr9-68wjVendor Advisories for CVE-2026-69186(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libcares2 (1.34.6-1ubuntu0.2) @ resolute | 2026-10-22 | ubuntu |
| redhat | c-ares-main-1.34.8-2.hum1 | 2026-07-16 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(2 across 2 ecosystems)
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| c-ares | 1.34.5-1, 1.34.5-1+deb13u1, 1.34.6-1, 1.34.7-1, 1.34.8-1 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| c-ares | 1.34.5-1, 1.34.6-1 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 7× in last 7d / 52× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 89 is merged into the row it repeats.
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-30 07:25 UTCOSV refresh
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
- 2026-10-25 14:09 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
- 2026-10-22 19:31 UTCEG score recompute
- 2026-10-22 19:31 UTCVendor advisory
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-18 03:19 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
Show 63 moreShow fewer
- 2026-10-12 15:44 UTCEG score recompute
- 2026-10-11 19:50 UTCVendor advisory
- 2026-10-11 19:29 UTCEG score recompute
- 2026-10-11 16:45 UTCEG score recompute
- 2026-10-11 14:05 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-10 19:57 UTCEG score recompute
- 2026-10-10 19:57 UTCVendor advisory
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-09 20:06 UTCVendor advisory
- 2026-10-08 20:14 UTCEG score recompute
- 2026-10-08 20:14 UTCVendor advisory
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-07 18:30 UTCVendor advisory
- 2026-10-06 18:38 UTCEG score recompute
- 2026-10-06 18:38 UTCVendor advisory
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-05 18:47 UTCEG score recompute
- 2026-10-05 18:47 UTCVendor advisory
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-04 18:49 UTCVendor advisory
- 2026-10-03 18:48 UTCEG score recompute
- 2026-10-03 18:48 UTCVendor advisory
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-02 18:17 UTCEG score recompute
- 2026-10-02 18:17 UTCVendor advisory
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-10-01 18:25 UTCVendor advisory
- 2026-09-30 18:14 UTCEG score recompute
- 2026-09-30 18:14 UTCVendor advisory
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-29 18:20 UTCEG score recompute
- 2026-09-29 18:20 UTCVendor advisory
- 2026-09-28 18:16 UTCEG score recompute
- 2026-09-28 18:16 UTCVendor advisory
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-27 18:06 UTCEG score recompute
- 2026-09-27 18:06 UTCVendor advisory
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-26 18:15 UTCEG score recompute
- 2026-09-26 18:15 UTCVendor advisory
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-25 18:21 UTCVendor advisory
- 2026-09-24 18:19 UTCEG score recompute
- 2026-09-24 18:19 UTCVendor advisory
- 2026-09-23 18:27 UTCEG score recompute
- 2026-09-23 18:27 UTCVendor advisory
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-22 19:57 UTCEG score recompute
- 2026-09-22 19:57 UTCVendor advisory
- 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-21 20:06 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-09-19 20:23 UTCEG score recompute
- 2026-09-18 20:31 UTCEG score recompute
- 2026-09-18 19:59 UTCEG score recompute
- 2026-09-18 18:27 UTCEG score recompute
- 2026-09-18 17:29 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
- 2026-09-18 17:29 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:13:c-ares
Same vendor
3 shownredhat:RHSA-2026:40574 · ubuntu:USN-8951-1
Frequently asked(5)
What is CVE-2026-69186?
When was the CVE record for CVE-2026-69186 published?
Is CVE-2026-69186 actively exploited?
What is the CVSS score of CVE-2026-69186?
How do I remediate CVE-2026-69186?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69186
Is Your Infrastructure Affected by CVE-2026-69186?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.