CVE-2026-69184

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-83213 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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
41st
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-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-27). 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 none (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 24, 2026

Advisory Details (6)

Auto-updated Sep 18, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
GitHub release Patch Available

1.34.7

Patch available: c-ares/c-ares v1.34.7

https://github.com/c-ares/c-ares/releases/tag/v1.34.7
GitHub commit

commit 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/f1288bbc70e9a1e0a77134c2382157e52d326aea
GitHub commit Patch Available

commit 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
GitHub pull request Patch Available

[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/1210
GitHub pull request

enforce 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/1164
GitHub advisoryMentions a patch (unverified)

CPU-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-gc76

Vendor Advisories for CVE-2026-69184(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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibcares2 (1.27.0-1.0ubuntu1.1) @ noble2026-10-27ubuntu
redhatc-ares-main-1.34.8-2.hum12026-07-16redhat

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)
PackageVulnerable rangeFix by version rangeDependents
c-ares1.34.5-1, 1.34.5-1+deb13u1, 1.34.6-1, 1.34.7-1, 1.34.8-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
c-ares1.34.5-1, 1.34.6-1
  • every version up to 1.34.7-1: fixed in 1.34.7-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 9× in last 7d / 69× 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.

Showing the most recent 97 of 123 refreshes on record for this CVE.

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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 26 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-27 18:54 UTCEG score recompute
  7. 2026-10-27 18:54 UTCVendor advisory
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-25 14:09 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-10-20 08:58 UTCEG score recompute
  18. 2026-10-20 08:58 UTCVendor advisory
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  21. 2026-10-18 03:19 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
Show 72 more
  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-10-13 09:55 UTCEG score recompute
  3. 2026-10-13 09:55 UTCVendor advisory
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  5. 2026-10-12 15:44 UTCEG score recompute
  6. 2026-10-11 23:00 UTCVendor advisory
  7. 2026-10-11 19:29 UTCEG score recompute
  8. 2026-10-11 16:45 UTCEG score recompute
  9. 2026-10-11 14:05 UTCEG score recompute
  10. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-11 11:23 UTCEG score recompute
  12. 2026-10-11 11:23 UTCVendor advisory
  13. 2026-10-10 23:45 UTCEG score recompute
  14. 2026-10-10 23:45 UTCVendor advisory
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-10-10 12:08 UTCVendor advisory
  17. 2026-10-10 00:33 UTCEG score recompute
  18. 2026-10-10 00:33 UTCVendor advisory
  19. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-10-09 13:01 UTCVendor advisory
  21. 2026-10-08 23:35 UTCEG score recompute
  22. 2026-10-08 23:35 UTCVendor advisory
  23. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-10-08 12:02 UTCVendor advisory
  25. 2026-10-08 00:21 UTCEG score recompute
  26. 2026-10-08 00:21 UTCVendor advisory
  27. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  28. 2026-10-07 12:48 UTCVendor advisory
  29. 2026-10-07 00:54 UTCEG score recompute
  30. 2026-10-07 00:54 UTCVendor advisory
  31. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  32. 2026-10-06 13:09 UTCVendor advisory
  33. 2026-10-06 01:34 UTCEG score recompute
  34. 2026-10-06 01:34 UTCVendor advisory
  35. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  36. 2026-10-05 13:47 UTCVendor advisory
  37. 2026-10-05 02:14 UTCEG score recompute
  38. 2026-10-05 02:14 UTCVendor advisory
  39. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  40. 2026-10-04 14:33 UTCVendor advisory
  41. 2026-10-04 03:01 UTCVendor advisory
  42. 2026-10-03 15:28 UTCEG score recompute
  43. 2026-10-03 15:28 UTCVendor advisory
  44. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  45. 2026-10-03 03:46 UTCEG score recompute
  46. 2026-10-03 03:46 UTCVendor advisory
  47. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  48. 2026-10-02 16:13 UTCVendor advisory
  49. 2026-10-02 16:12 UTCVendor advisory
  50. 2026-10-02 16:12 UTCVendor advisory
  51. 2026-10-02 04:37 UTCEG score recompute
  52. 2026-10-02 04:37 UTCVendor advisory
  53. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  54. 2026-10-01 17:04 UTCVendor advisory
  55. 2026-10-01 05:03 UTCVendor advisory
  56. 2026-09-30 17:30 UTCEG score recompute
  57. 2026-09-30 17:30 UTCVendor advisory
  58. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  59. 2026-09-30 05:53 UTCVendor advisory
  60. 2026-09-29 18:20 UTCEG score recompute
  61. 2026-09-29 18:20 UTCVendor advisory
  62. 2026-09-29 05:48 UTCEG score recompute
  63. 2026-09-29 05:48 UTCVendor advisory
  64. 2026-09-28 18:16 UTCEG score recompute
  65. 2026-09-28 18:16 UTCVendor advisory
  66. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  67. 2026-09-28 06:26 UTCVendor advisory
  68. 2026-09-27 18:53 UTCEG score recompute
  69. 2026-09-27 18:53 UTCVendor advisory
  70. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  71. 2026-09-27 07:21 UTCVendor advisory
  72. 2026-09-26 19:48 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-69184?
CVE-2026-69184 is a high-severity vulnerability; its CVE record was published on September 18, 2026. 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…
When was the CVE record for CVE-2026-69184 published?
The CVE record for CVE-2026-69184 was published on September 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-69184 actively exploited?
CVE-2026-69184 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69184?
CVE-2026-69184 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69184?
A fix for CVE-2026-69184 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69184 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69184

Explore →

Is Your Infrastructure Affected by CVE-2026-69184?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.