VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

irrd: vulnerability history, versions and safety

irrd is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 9 releases, from Mar 2022 to Mar 2026. 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 H2 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 06 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all irrd vulnerabilities

Vulert verdict on irrd 4.5.4 i

Updated on 23 Oct 2026

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

Package health score 68/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 4.5.4 — unaffected i
  • Vulnerabilities on record 4 over 3 years · 2 in the last year i
  • Latest disclosure 06 Mar 2026 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Stars 189 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence non-standard 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 irrd, 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
4.5.4 19 Oct 2026 none non-standard — Details →
4.4.8 19 Oct 2026 none non-standard — Details →
4.5.3 30 Jun 2026 none non-standard — Details →
4.4.7 30 Jun 2026 none non-standard — Details →
4.5.2 28 Mar 2026 none non-standard — Details →
4.4.6 28 Mar 2026 none non-standard — Details →
4.5.1 04 Mar 2026 none non-standard — Details →
4.4.5 04 Mar 2026 none non-standard — Details →
4.5.0 30 Jan 2026 U1 non-standard Yes Details →
4.4.4 25 Apr 2024 H1 U1 non-standard Yes Details →
4.3.3 25 Apr 2024 none BSD-2-Clause — Details →
4.4.3 25 Jan 2024 H1 U1 non-standard Yes Details →
4.3.2 25 Jan 2024 none BSD-2-Clause — Details →
4.4.2 17 Oct 2023 H1 U1 non-standard Yes Details →
4.4.1 12 Oct 2023 H1 U1 non-standard Yes Details →
4.4.0 28 Sep 2023 H1 U1 non-standard Yes Details →
4.3.1 17 Aug 2023 none BSD-2-Clause — Details →
4.2.9 17 Aug 2023 none BSD-2-Clause — Details →
4.3.0.post1 09 Jun 2023 none BSD-2-Clause — Details →
4.3.0 06 Jun 2023 none BSD-2-Clause — Details →
4.2.8 21 Apr 2023 none BSD-2-Clause — Details →
4.2.7 15 Feb 2023 none BSD-2-Clause — Details →
4.2.6 18 Nov 2022 none BSD-2-Clause — Details →
4.2.5 24 Jun 2022 none BSD-2-Clause — Details →
4.2.4 05 Apr 2022 none BSD-2-Clause — Details →
4.2.3 31 Mar 2022 none BSD-2-Clause — Details →
4.2.2 02 Dec 2021 H1 U1 BSD-2-Clause Yes Details →
4.2.1 29 Oct 2021 H1 U1 BSD-2-Clause Yes Details →
4.1.8 29 Oct 2021 none BSD-2-Clause — Details →
4.2.0 15 Sep 2021 H1 U1 BSD-2-Clause Yes Details →
4.1.7 07 Sep 2021 none BSD-2-Clause — Details →
4.1.6 30 Aug 2021 none BSD-2-Clause — Details →
4.1.5 24 Aug 2021 none BSD-2-Clause — Details →
4.1.4 18 Jun 2021 none BSD-2-Clause — Details →
4.1.3 15 Jun 2021 none BSD-2-Clause — Details →
4.1.2 10 Feb 2021 none non-standard — Details →
4.1.1 10 Dec 2020 none non-standard — Details →
4.1.0 15 Sep 2020 none non-standard — Details →
4.0.8 12 Nov 2019 none non-standard — Details →
4.0.7 03 Oct 2019 none non-standard — Details →
4.0.6 05 Sep 2019 none non-standard — Details →
4.0.5.post1 02 Sep 2019 none non-standard — Details →
4.0.4.post1 15 Jul 2019 none non-standard — Details →
4.0.4 15 Jul 2019 none non-standard — Details →
4.0.3 29 Jun 2019 none non-standard — Details →
4.0.2 26 Jun 2019 none non-standard — Details →
4.0.1 11 Jun 2019 none non-standard — Details →
4.0.0 02 May 2019 none non-standard — Details →
4.0.0rc1 20 Dec 2018 none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for irrd

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-28681: IRRd Password Reset Poisoning via Host Header Injection 8.1 high 4.4.5 04 Mar 2026
CVE-2026-28681: IRRD Package Vulnerability Allows Account Takeover via Host Header Manipulation 8.1 high 4.4.5 06 Mar 2026
CVE-2022-24798: Improper Removal of Sensitive Information Before Storage or Transfer in irrd 7.5 high 4.2.3 01 Apr 2022
CVE-2022-24798: Internet Routing Registry Daemon (IRRD) Password Hash Disclosure N/A unrated fdffaf8dd71713f06e99dff417e6aa1e6fa84b70 31 Mar 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 irrd

Is irrd safe to use?

Vulert records 4 vulnerabilities for irrd in PyPI: 0 critical, 2 high, 0 medium and 0 low, plus 2 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 irrd's Vulert package health score?

Vulert scores irrd 68/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).

Is the latest version of irrd affected?

No. 4.5.4, 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.

How many vulnerabilities does irrd have?

4 vulnerabilities are recorded for irrd in the PyPI ecosystem: 0 critical, 2 high, 0 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 irrd vulnerabilities disclosed?

2 vulnerabilities were recorded for irrd in the last 12 months, and the oldest entry in this database dates to 31 Mar 2022. 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 irrd 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 irrd for upcoming vulnerabilities?

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