VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

dnspython: vulnerability history, versions and safety

dnspython is a package in the PyPI ecosystem. Vulert records 1 vulnerability for it across 25 releases, first recorded in Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all dnspython vulnerabilities

Vulert verdict on dnspython 2.9.0 i

Updated on 23 Oct 2026

Good news: 2.9.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 87/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 2.9.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.9.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.9.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Depended on by 20,821 packages i
  • Stars 2,686 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence ISC i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for dnspython, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.9.0 09 Oct 2026 none ISC — Details →
2.8.0 07 Sep 2025 none ISC — Details →
2.8.0rc1 01 Sep 2025 none ISC — Details →
2.7.0 05 Oct 2024 none ISC — Details →
2.7.0rc1 21 Sep 2024 none ISC — Details →
2.6.1 18 Feb 2024 none ISC — Details →
2.6.0 16 Feb 2024 U1 ISC Yes Details →
2.6.0rc1 10 Feb 2024 U1 ISC Yes Details →
2.5.0 20 Jan 2024 U1 ISC Yes Details →
2.5.0rc1 06 Jan 2024 U1 ISC Yes Details →
2.4.2 09 Aug 2023 U1 ISC Yes Details →
2.4.1 26 Jul 2023 U1 ISC Yes Details →
2.4.0 15 Jul 2023 U1 ISC Yes Details →
2.4.0rc1 04 Jul 2023 U1 ISC Yes Details →
2.3.0 15 Jan 2023 U1 ISC Yes Details →
2.3.0rc1 27 Dec 2022 U1 ISC Yes Details →
2.2.1 06 Mar 2022 U1 ISC Yes Details →
2.2.0 18 Jan 2022 U1 ISC Yes Details →
2.2.0rc1 21 Dec 2021 U1 ISC Yes Details →
2.1.0 07 Jan 2021 U1 ISC Yes Details →
2.1.0rc1 30 Oct 2020 U1 ISC Yes Details →
2.0.0 17 Jul 2020 U1 ISC Yes Details →
2.0.0rc2 04 Jul 2020 U1 ISC Yes Details →
2.0.0rc1 20 Jun 2020 U1 ISC Yes Details →
1.16.0 08 Dec 2018 U1 non-standard Yes Details →
1.15.0 08 Oct 2016 U1 non-standard Yes Details →
1.14.0 27 May 2016 U1 non-standard Yes Details →
1.13.0 10 May 2016 U1 non-standard Yes Details →
1.12.0 01 Sep 2014 U1 non-standard Yes Details →
1.11.1 02 Sep 2013 U1 non-standard Yes Details →
1.11.0 22 Jul 2013 U1 non-standard Yes Details →

All 31 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for dnspython

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-29483: dnspython Vulnerability Leading to Potential DoS via Tudoor Mechanism 5.9 medium 2.6.1 07 Jul 2026

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 dnspython

Is dnspython safe to use?

Vulert records 1 vulnerabilities for dnspython in PyPI: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is dnspython's Vulert package health score?

Vulert scores dnspython 87/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of dnspython affected?

No. 2.9.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of dnspython should I use?

2.9.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does dnspython have?

1 vulnerability is recorded for dnspython in the PyPI ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 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 dnspython vulnerabilities disclosed?

1 vulnerability was recorded for dnspython in the last 12 months, and the oldest entry in this database dates to 07 Jul 2026. 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 dnspython 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 dnspython for upcoming vulnerabilities?

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