pycares is vulnerable to a use-after-free condition that occurs when a Channel object is garbage collected while DNS queries are still pending.
Full advisory text at GitHub advisory.
pypi package report
Is pycares safe?
pycares (pypi) has 2 known vulnerabilities, the worst rated MODERATE. Upgrade to 4.9.0 or later to clear all of them. No malicious-package signal is recorded.
// ai model usage
No published models are known to use this package.
cvss
5.0
medium
severity band, no base score published
epss
not scored
chance of exploitation in 30 days
xyz score
not scored
CyberXYZ composite out of 10
fig. 01 — GHSA-5qpg-rh4j-qp35, the advisory selected below
// 2 advisories
Is pycares safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 2 known vulnerabilities for pycares (pypi), the worst rated MODERATE, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does pycares have known vulnerabilities?
Yes. CyberXYZ records 2 known vulnerabilities for pycares (pypi), the worst rated MODERATE. They are GHSA-5qpg-rh4j-qp35, GHSA-c58j-88f5-h53f.
Which version of pycares should I use?
4.9.0 or later clears every advisory recorded for pycares (pypi). Check the release you pick before installing it.
How do I check pycares before installing?
Search pycares in CyberXYZ Check at https://cyberxyz.io/check?q=pycares. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 11:00 UTC. The most recent advisory here was published 2025-06-16. Updated continuously from NVD, GHSA, OSV and CNA feeds.