VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

designate: vulnerability history, versions and safety

designate is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 64 releases, from Aug 2017 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H1 M1 U2
i
4 with no fix published

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

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

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all designate vulnerabilities

Vulert verdict on designate 23.0.0 i

Updated on 23 Oct 2026

Careful: 23.0.0 has 4 known vulnerabilities, and 4 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 23.0.0 — affected i
  • Vulnerabilities on record 4 over 4 years · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 6.5 i
  • With no published fix 4 i
  • Depended on by 1 packages i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 designate, 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
23.0.0 30 Sep 2026 H1 M1 U2 Apache-2.0 No Details →
23.0.0.0rc1 10 Sep 2026 H1 M1 U2 Apache-2.0 No Details →
20.0.2 11 Aug 2026 H1 M1 U2 non-standard No Details →
22.0.1 11 Aug 2026 H1 M1 U2 non-standard No Details →
21.0.1 11 Aug 2026 H1 M1 U2 non-standard No Details →
20.0.1 20 Jul 2026 H1 M1 U2 non-standard No Details →
22.0.0 01 Apr 2026 H1 M1 U2 non-standard No Details →
22.0.0.0rc1 11 Mar 2026 H1 M1 U2 non-standard No Details →
19.1.0 26 Jan 2026 H1 M1 U2 non-standard No Details →
21.0.0 01 Oct 2025 H1 M1 U2 Apache-2.0 No Details →
21.0.0.0rc1 11 Sep 2025 H1 M1 U2 Apache-2.0 No Details →
18.1.0 25 Jul 2025 H1 M1 U2 Apache-2.0 No Details →
17.0.2 24 Apr 2025 H1 M1 U2 Apache-2.0 No Details →
20.0.0 02 Apr 2025 H1 M1 U2 Apache-2.0 No Details →
20.0.0.0rc1 18 Mar 2025 H1 M1 U2 Apache-2.0 No Details →
19.0.0 02 Oct 2024 H1 M1 U2 non-standard No Details →
19.0.0.0rc1 16 Sep 2024 H1 M1 U2 non-standard No Details →
18.0.0 03 Apr 2024 H1 M1 U2 non-standard No Details →
18.0.0.0rc1 15 Mar 2024 H1 M1 U2 non-standard No Details →
17.0.1 08 Dec 2023 H1 M1 U2 non-standard No Details →
14.0.4 08 Dec 2023 H1 M1 U2 non-standard No Details →
16.0.2 08 Dec 2023 H1 M1 U2 non-standard No Details →
15.0.2 08 Dec 2023 H1 M1 U2 non-standard No Details →
17.0.0 04 Oct 2023 H1 M1 U2 non-standard No Details →
17.0.0.0rc2 27 Sep 2023 H1 M1 U2 non-standard No Details →
15.0.1 21 Sep 2023 H1 M1 U2 non-standard No Details →
17.0.0.0rc1 15 Sep 2023 H1 M1 U2 non-standard No Details →
14.0.3 28 Jul 2023 H1 M1 U2 non-standard No Details →
16.0.1 13 Jul 2023 H1 M1 U2 non-standard No Details →
14.0.2 23 Mar 2023 H1 M1 U2 non-standard No Details →
16.0.0 22 Mar 2023 H1 M1 U2 non-standard No Details →
16.0.0.0rc1 06 Mar 2023 H1 M1 U2 non-standard No Details →
13.0.2 18 Jan 2023 H1 M1 U2 non-standard No Details →
15.0.0 05 Oct 2022 H1 M1 U2 non-standard No Details →
15.0.0.0rc2 22 Sep 2022 H1 M1 U2 non-standard No Details →
15.0.0.0rc1 16 Sep 2022 H1 M1 U2 non-standard No Details →
12.1.0 17 Jun 2022 H1 M1 U2 non-standard No Details →
13.0.1 09 Jun 2022 H1 M1 U2 non-standard No Details →
14.0.1 09 Jun 2022 H1 M1 U2 non-standard No Details →
11.0.2 07 Apr 2022 H1 M1 U2 non-standard No Details →
14.0.0 30 Mar 2022 H1 M1 U2 non-standard No Details →
14.0.0.0rc1 10 Mar 2022 H1 M1 U2 non-standard No Details →
11.0.1 03 Dec 2021 H1 M1 U2 non-standard No Details →
12.0.1 03 Dec 2021 H1 M1 U2 non-standard No Details →
10.0.2 03 Dec 2021 H1 M1 U2 non-standard No Details →
13.0.0 06 Oct 2021 H1 M1 U2 non-standard No Details →
13.0.0.0rc1 17 Sep 2021 H1 M1 U2 non-standard No Details →
10.0.1 26 Jul 2021 H1 M1 U2 non-standard No Details →
12.0.0 14 Apr 2021 H1 M1 U2 non-standard No Details →
12.0.0.0rc1 26 Mar 2021 H1 M1 U2 non-standard No Details →
9.0.2 16 Feb 2021 H1 M1 U2 non-standard No Details →
11.0.0 14 Oct 2020 H1 M1 U2 non-standard No Details →
11.0.0.0rc1 25 Sep 2020 H1 M1 U2 non-standard No Details →
8.0.1 23 Jul 2020 H1 M1 U2 non-standard No Details →
9.0.1 18 Jun 2020 H1 M1 U2 non-standard No Details →
10.0.0 13 May 2020 H1 M1 U2 non-standard No Details →
10.0.0.0rc2 07 May 2020 H1 M1 U2 non-standard No Details →
10.0.0.0rc1 23 Apr 2020 H1 M1 U2 non-standard No Details →
7.0.1 09 Mar 2020 H1 M1 U2 non-standard No Details →
9.0.0 16 Oct 2019 H1 M1 U2 non-standard No Details →
9.0.0.0rc1 27 Sep 2019 H1 M1 U2 non-standard No Details →
5.0.3 26 Apr 2019 H1 M1 U2 non-standard No Details →
8.0.0 10 Apr 2019 H1 M1 U2 non-standard No Details →
8.0.0.0rc1 21 Mar 2019 H1 M1 U2 non-standard No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2019 1
  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for designate

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2015-5695: Designate Denial of Service Vulnerability in OpenStack Kilo 6.5 medium No fix published 31 Aug 2017
CVE-2015-5694: Designate DNS Protocol Limit Bypass Vulnerability 6.5 medium No fix published 22 Nov 2019
CVE-2015-5694: Designate Package Record Set Size Limit Bypass Vulnerability 6.5 medium No fix published 24 May 2022
CVE-2015-5695: Designate Package Denial of Service via Large RecordSets 6.5 high No fix published 17 May 2022

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 designate

Is designate safe to use?

Vulert records 4 vulnerabilities for designate in PyPI: 0 critical, 1 high, 1 medium and 0 low, plus 2 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is designate's Vulert package health score?

Vulert scores designate 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of designate affected?

Yes. 23.0.0, the version you would install today, has 4 known vulnerabilities, and 4 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of designate should I use?

23.0.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 designate have?

4 vulnerabilities are recorded for designate in the PyPI ecosystem: 0 critical, 1 high, 1 medium and 0 low, plus 2 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 designate vulnerabilities disclosed?

0 vulnerabilities were recorded for designate in the last 12 months, and the oldest entry in this database dates to 31 Aug 2017. 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 designate 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 designate for upcoming vulnerabilities?

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