CVE-2026-28681: IRRd Web UI Host Header Injection Vulnerability

HIGH
Advisory Identifier: GHSA-22m3-c7vp-49fj
CVSS 8.1
CWE-640 CWE-601
Published
Advisory Summary

CVE-2026-28681 is a HIGH (CVSS 8.1) web ui host header injection vulnerability (CWE-640: Weak Password Recovery Mechanism for Forgotten Password) affecting IRRd libraries in the PyPI ecosystem. The issue involves web ui host header injection allows password reset poisoning via attacker-controlled email links. Remediation is available by upgrading affected packages to version 4.4.5, 4.5.1.

CVE-2026-28681 at a Glance

CVE Identifier CVE-2026-28681
GHSA Identifier GHSA-22m3-c7vp-49fj
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-640: Weak Password Recovery Mechanism for Forgotten Password
Affected Product IRRd
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-28681

To remediate this vulnerability, upgrade all affected IRRd dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

irrd fixed: 4.4.5
pip install irrd>=4.4.5
irrd fixed: 4.5.1
pip install irrd>=4.5.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show irrd

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-28681, inspect your installed packages using pip:

pip show irrd

Analyze the terminal output to locate any version of IRRd in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.4.5), your application is affected.

Note: The pip show irrd command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-640: Weak Password Recovery Mechanism for Forgotten Password, where the product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak. In IRRd, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Impact An attacker can manipulate the HTTP `Host` header on a password reset or account creation request. The confirmation link in the resulting email can then point to an attacker-controlled domain. Opening the link in the email is sufficient to pass the token to the attacker, who can then use it on the real IRRD instance to take over the account. A compromised account can then be used to modify RPSL objects maintained by the account's mntners and perform other account actions. If the user had two-factor authentication configured, which is required for users with override access, an attacker is not able to log in, even after successfully resetting the password. This issue affects IRRD 4.5.0 and all 4.4.x versions prior to 4.4.5. IRRD 4.3 and earlier are not affected, as they did not include the web UI. ## Cause Email links in account creation, password reset, and mntner migration emails were generated from the HTTP request context, allowing an attacker to manipulate the HTTP `Host` header to redirect these links to an attacker-controlled domain (password reset poisoning). ## Resolution Requests with a `Host` header that does not match `server.http.url` are now rejected, preventing Host header injection attacks against the web UI. All existing password reset tokens are invalidated by this upgrade, rendering any tokens that may have been captured by an attacker unusable. Patched versions: 4.4.5 and 4.5.1. ## Workarounds Configuring a reverse proxy (such as nginx) to reject requests where the `Host` header does not match the expected hostname is an effective workaround. Enabling two-factor authentication is strongly recommended for all users, as it prevents account takeover even if a password reset token is compromised. ## Detecting exploitation Because the victim never interacts with the real IRRD instance in this attack, it is difficult to detect exploitation from logs alone. Indicators that an account was targeted or compromised: - A `password reset email requested` followed by `password (re)set successfully` where the delay is longer than expected. Legitimate users actively waiting for a reset email tend to complete it quickly; victims who receive an unexpected email are less likely to click it immediately, resulting in a longer delay. - Users receiving a password reset mail without requesting one. - If a successfully attacked user later attempts to log in with their original password, this appears in the logs as `user failed login due to invalid account or password`. After upgrading to a patched release, all existing password reset tokens are invalidated. Users who can still log in with their password after the upgrade can be certain their account has not been taken over.

CVE-2026-28681 Affected IRRd Versions

2 component(s)
Fixed Versions:
4.4.54.5.1
Product / Package Ecosystem Affected Versions Fixed Version
irrd
PyPI
≥ 4.4.0
< 4.4.5
4.4.5
irrd
PyPI
≥ 4.5.0
< 4.5.1
4.5.1

References

Frequently Asked Questions

What is CVE-2026-28681?
CVE-2026-28681 is a security vulnerability in IRRd involving web UI host header injection allows password reset poisoning via attacker-controlled email links under CWE-640: Weak Password Recovery Mechanism for Forgotten Password.
Which IRRd versions are affected?
Affected versions include releases prior to 4.4.5, 4.5.1 across affected packages: irrd.
What version fixes CVE-2026-28681?
Upgrading to 4.4.5, 4.5.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is irrd affected?
Yes, irrd is affected in releases prior to 4.4.5, 4.5.1. Upgrade your dependency to 4.4.5, 4.5.1 or later.
What is the CVSS score of CVE-2026-28681?
CVE-2026-28681 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2026-28681?
CVE-2026-28681 is classified under CWE-640: Weak Password Recovery Mechanism for Forgotten Password (The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.).
How can I check PyPI dependencies for CVE-2026-28681?
Run the dependency tree command: 'pip show irrd'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-22m3-c7vp-49fj",
  "modified" : "2026-03-06T15:16:30Z",
  "published" : "2026-03-04T20:33:21Z",
  "aliases" : [ "CVE-2026-28681" ],
  "summary" : "IRRd: web UI host header injection allows password reset poisoning via attacker-controlled email links",
  "details" : "## Impact\n\nAn attacker can manipulate the HTTP `Host` header on a password reset or account creation request. The confirmation link in the resulting email can then point to an attacker-controlled domain. Opening the link in the email is sufficient to pass the token to the attacker, who can then use it on the real IRRD instance to take over the account. A compromised account can then be used to modify RPSL objects maintained by the account's mntners and perform other account actions.\n\nIf the user had two-factor authentication configured, which is required for users with override access, an attacker is not able to log in, even after successfully resetting the password.\n\nThis issue affects IRRD 4.5.0 and all 4.4.x versions prior to 4.4.5. IRRD 4.3 and earlier are not affected, as they did not include the web UI.\n\n## Cause\n\nEmail links in account creation, password reset, and mntner migration emails were generated from the HTTP request context, allowing an attacker to manipulate the HTTP `Host` header to redirect these links to an attacker-controlled domain (password reset poisoning).\n\n## Resolution\n\nRequests with a `Host` header that does not match `server.http.url` are now rejected, preventing Host header injection attacks against the web UI.\n\nAll existing password reset tokens are invalidated by this upgrade, rendering any tokens that may have been captured by an attacker unusable.\n\nPatched versions: 4.4.5 and 4.5.1.\n\n## Workarounds\n\nConfiguring a reverse proxy (such as nginx) to reject requests where the `Host` header does not match the expected hostname is an effective workaround. Enabling two-factor authentication is strongly recommended for all users, as it prevents account takeover even if a password reset token is compromised.\n\n## Detecting exploitation\n\nBecause the victim never interacts with the real IRRD instance in this attack, it is difficult to detect exploitation from logs alone.\n\nIndicators that an account was targeted or compromised:\n\n- A `password reset email requested` followed by `password (re)set successfully` where the delay is longer than expected. Legitimate users actively waiting for a reset email tend to complete it quickly; victims who receive an unexpected email are less likely to click it immediately, resulting in a longer delay.\n- Users receiving a password reset mail without requesting one.\n- If a successfully attacked user later attempts to log in with their original password, this appears in the logs as `user failed login due to invalid account or password`.\n\nAfter upgrading to a patched release, all existing password reset tokens are invalidated. Users who can still log in with their password after the upgrade can be certain their account has not been taken over.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "irrd"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.4.0"
      }, {
        "fixed" : "4.4.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "irrd"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.5.0"
      }, {
        "fixed" : "4.5.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/irrdnet/irrd/security/advisories/GHSA-22m3-c7vp-49fj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-28681"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/irrdnet/irrd/commit/8408e0f1b9f47eb2f2e712d6153e32194df05fbb"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/irrdnet/irrd/commit/cf62df4a49d3891e80b2879d9b324d1af050000c"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/irrdnet/irrd"
  }, {
    "type" : "WEB",
    "url" : "https://irrd.readthedocs.io/en/stable/releases/4.4.5"
  }, {
    "type" : "WEB",
    "url" : "https://irrd.readthedocs.io/en/stable/releases/4.5.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-601", "CWE-640" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-04T20:33:21Z",
    "nvd_published_at" : "2026-03-06T05:16:37Z"
  }
}