CVE-2026-33630

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.8% (58th 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

Also known asEUVD-2026-70664 (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.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

c-ares is an asynchronous resolver library. From ver 1.32.3 until 1.34.7, a use-after-free / double-free in c-ares' query-completion handling. The same flaw — a query's callback being invoked while the query is still linked in the channel's internal lookup structures — is present at multiple points in the resend/finish path (timeout handling, response handling, and query dispatch). If the query, or for ares_getaddrinfo() the owning host_query, is freed as a side effect of that callback, it is then accessed and/or freed a second time. This vulnerability is fixed in ver 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.8% × 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.8%
EPSS %ILE
58th
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.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). 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 3, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Sep 3, 2026
Patch available. Sources: github_release, github, 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 Patch Available

commit d823199b6880 (c-ares/c-ares)

Patch available: c-ares/c-ares v1.34.7 (contains commit d823199b6880)

https://github.com/c-ares/c-ares/commit/d823199b688052dcdc1646f2ab4cb8c16b1c644a
GitHub advisoryMentions a patch (unverified)

Use-after-free / double-free in c-ares query-completion handling, remotely triggerable via ares_getaddrinfo() over TCP · Advisory · c-ares/c-ares · GitHub

https://github.com/c-ares/c-ares/security/advisories/GHSA-6wfj-rwm7-3542

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibcares2 (1.34.6-1ubuntu0.1) @ resolute2026-10-24ubuntu
redhatc-ares-0:1.34.6-2.el10_22026-07-20redhat
redhatc-ares-main-1.34.7-1.hum12026-07-07redhat

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

(6 across 6 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
c-ares—
  • every version up to 1.34.8-r0: fixed in 1.34.8-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
c-ares—
  • every version up to 1.34.8-r0: fixed in 1.34.8-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
c-ares—
  • every version up to 1.34.8-r0: fixed in 1.34.8-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
c-ares—
  • every version up to 1.34.8-r0: fixed in 1.34.8-r0
—
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(2)

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 8× in last 7d / 34× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 190 rows 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. None are among the latest 100 rows. The 90 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-33630?
CVE-2026-33630 is a high-severity vulnerability; its CVE record was published on September 3, 2026. c-ares is an asynchronous resolver library. From ver 1.32.3 until 1.34.7, a use-after-free / double-free in c-ares' query-completion handling. The same flaw — a query's callback being invoked while the query is still linked in the channel's internal lookup structures — is present at multiple points…
When was the CVE record for CVE-2026-33630 published?
The CVE record for CVE-2026-33630 was published on September 3, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-33630 actively exploited?
CVE-2026-33630 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33630?
CVE-2026-33630 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-33630?
A fix for CVE-2026-33630 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-33630 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-33630

Explore →

Is Your Infrastructure Affected by CVE-2026-33630?

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