CVE-2026-28681: IRRd Password Reset Poisoning via Host Header Injection
Summary
CVE-2026-28681: IRRd: web UI host header injection allows password reset poisoning via attacker-controlled email links. Affects irrd across 2 version ranges.
>= 4.4.0, < 4.4.5
>= 4.5.0, < 4.5.1
Fixed in 4.4.5 or 4.5.1, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
IRRd is an open-source software package that facilitates the management of Internet Routing Registries. It provides a web UI for users to create and manage their accounts, including functionalities for password resets and account creation. However, certain versions of IRRd are vulnerable to a Host header injection attack, which can lead to serious security issues.
Vulnerability Detail
The vulnerability arises from the way IRRd generates email links for password resets and account creation. An attacker can manipulate the HTTP Host header in these requests, allowing them to craft a confirmation link that points to a malicious domain. If a user clicks on this link, the attacker can capture the password reset token and use it to take over the user's account. This can lead to unauthorized modifications of RPSL objects and other account actions. Although two-factor authentication can mitigate the risk of account takeover, it does not prevent the initial exploitation of the vulnerability.
How To Fix
Latest published version: 4.5.4 as of 23 Oct 2026
pip install --upgrade "irrd==4.5.4"
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
>= 4.4.0, < 4.4.54.4.5pip install --upgrade "irrd==4.4.5" -
>= 4.5.0, < 4.5.14.5.1pip install --upgrade "irrd==4.5.1"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary workaround, configure a reverse proxy (such as nginx) to reject requests where the Host header does not match the expected hostname. Here is an example nginx configuration snippet:
server {
listen 80;
server_name your_expected_hostname;
location / {
if ($host != 'your_expected_hostname') {
return 444;
}
proxy_pass http://your_backend;
}
}
Additionally, enabling two-factor authentication for all users is strongly recommended to prevent account takeover even if a password reset token is compromised.
Conclusion
The IRRd vulnerability CVE-2026-28681 poses a significant risk through Host header injection, allowing attackers to hijack password reset processes. Users are encouraged to update to the patched versions and implement recommended workarounds to secure their accounts.
See every vulnerability recorded for irrd →
FAQ
IRRd versions 4.4.0 to 4.4.4 and 4.5.0 are affected. Versions 4.4.5 and 4.5.1 have patched the vulnerability.
Look for unexpected password reset emails or unusual login attempts in your account activity. If you receive a reset email without requesting one, your account may have been targeted.
Immediately change your password and enable two-factor authentication if you haven't already. Monitor your account for any unauthorized changes.
Detection is challenging since the victim interacts with a malicious site. However, unusual delays between password reset requests and successful resets can be an indicator.
Vulert monitors open-source vulnerabilities in your software using the Pipfile.lock. You can check if your application is affected by this vulnerability using the Vulert playground without signing up.
References
Related vulnerabilities
Recent vulnerabilities recorded for irrd.