c-ares is an asynchronous resolver library. Prior to 1.34.7, ares_dns_name_parse() enforces backward DNS compression pointers but does not bound the total pointer hops or assembled name length. A malicious DNS server can send a response containing a long descending pointer chain and many resource records whose NAME or RDATA fields refer to the chain, causing repeated decompression work that grows quadratically with message size. A single crafted response can stall the single-threaded c-ares event loop and deny DNS resolution, without causing memory corruption or information disclosure. This issue is fixed in version 1.34.7.
CVE-2026-69184
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(low)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (6)
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 f1288bbc70e9 (c-ares/c-ares)
Fix landed in c-ares/c-ares commit f1288bbc70e9 — awaiting tagged release
https://github.com/c-ares/c-ares/commit/f1288bbc70e9a1e0a77134c2382157e52d326aeacommit 5c8341ba6ff3 (c-ares/c-ares)
Patch available: c-ares/c-ares v1.34.7 (contains commit 5c8341ba6ff3)
https://github.com/c-ares/c-ares/commit/5c8341ba6ff3a8e4e4dfd616f8ed0418838b8b7b[Backport v1.34] enforce 255 octet name limit when parsing dns names
Patch available: c-ares/c-ares v1.34.7 (PR #1210 merged 2026-07-05)
https://github.com/c-ares/c-ares/pull/1210enforce 255 octet name limit when parsing dns names
Fix merged in c-ares/c-ares PR #1164 on 2026-07-02 — awaiting tagged release
https://github.com/c-ares/c-ares/pull/1164CPU-exhaustion denial of service via unbounded DNS name compression pointer chains · Advisory · c-ares/c-ares · GitHub
https://github.com/c-ares/c-ares/security/advisories/GHSA-pjmc-gx33-gc76Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-09-18 18:27 UTCEG score recompute
- 2026-09-18 17:34 UTCEG score recompute
- 2026-09-18 17:34 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-69184?
When was CVE-2026-69184 disclosed?
What is the CVSS score of CVE-2026-69184?
How do I remediate CVE-2026-69184?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-69184
Is Your Infrastructure Affected by CVE-2026-69184?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.