VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

c-ares: vulnerability history, versions and safety

c-ares is a package in the Debian ecosystem. Vulert records 8 vulnerabilities for it across 5 releases, from Nov -0001 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded U8
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 10 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all c-ares vulnerabilities

Vulert verdict on c-ares i

Updated on 23 Oct 2026

Careful: 3 of the 8 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 8 vulnerabilities on record across 2026 years, 3 in the last year.

What to do: Plan around the 3 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 8 over 2026 years · 3 in the last year i
  • Latest disclosure 10 Aug 2026 i
  • Highest CVSS n/a i
  • With no published fix 3 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for c-ares, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
1.34.8-1 U2 No Details →
1.34.7-1 U2 No Details →
1.34.6-1 U2 No Details →
1.34.5-1 U4 No Details →
1.34.5-1+deb13u1 U2 No Details →

Newest 5 of 5 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2023 2
  • 2024 1
  • 2025 2
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 8 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for c-ares

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
C-ares Vulnerability: Insufficient Entropy in Cross-Compilation Leading to Potential Security Risks N/A unrated 1.19.1-2 25 May 2023
Predictable Random Number Generation in c-ares Library N/A unrated 1.19.1-2 25 May 2023
Critical Memory Access Vulnerability in c-ares Package N/A unrated 1.27.0-1 23 Feb 2024
Use-After-Free Vulnerability in c-ares Package N/A unrated 1.34.5-1 08 Apr 2025
Critical Vulnerability in c-ares Package: CVE-2025-62408 N/A unrated No fix published 30 Nov -0001

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About c-ares

Is c-ares safe to use?

Vulert records 8 vulnerabilities for c-ares in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 8 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does c-ares have?

8 vulnerabilities are recorded for c-ares in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 8 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new c-ares vulnerabilities disclosed?

3 vulnerabilities were recorded for c-ares in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of c-ares are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor c-ares for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the c-ares version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.