{ "document": { "category": "csaf_base", "csaf_version": "2.0", "distribution": { "tlp": { "label": "WHITE" } }, "lang": "en", "notes": [ { "category": "legal_disclaimer", "text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings." } ], "publisher": { "category": "coordinator", "contact_details": "cert@ncsc.nl", "name": "National Cyber Security Centre", "namespace": "https://www.ncsc.nl/" }, "title": "CVE-2026-28681", "tracking": { "current_release_date": "2026-03-23T03:56:19.872542Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-28681", "initial_release_date": "2026-03-04T20:39:46.851897Z", "revision_history": [ { "date": "2026-03-04T20:39:46.851897Z", "number": "1", "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (6).| CWES updated (1)." }, { "date": "2026-03-04T20:39:48.973289Z", "number": "2", "summary": "NCSC Score created." }, { "date": "2026-03-05T00:36:27.885368Z", "number": "3", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (8).| Product Identifiers created (6).| References created (5).| CWES updated (1)." }, { "date": "2026-03-05T00:36:36.802221Z", "number": "4", "summary": "NCSC Score updated." }, { "date": "2026-03-06T05:25:27.062925Z", "number": "5", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (5).| CWES updated (1)." }, { "date": "2026-03-06T05:25:29.894007Z", "number": "6", "summary": "NCSC Score updated." }, { "date": "2026-03-06T05:39:06.180105Z", "number": "7", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products connected (2).| References created (5).| CWES updated (1)." }, { "date": "2026-03-06T05:39:07.966140Z", "number": "8", "summary": "NCSC Score updated." }, { "date": "2026-03-06T09:26:55.577330Z", "number": "9", "summary": "NCSC Score updated." }, { "date": "2026-03-06T14:52:46.379321Z", "number": "10", "summary": "Source created.| CVE status created. (valid)| EPSS created." }, { "date": "2026-03-06T16:00:49.937816Z", "number": "11", "summary": "References created (1)." }, { "date": "2026-03-06T16:39:13.063381Z", "number": "12", "summary": "Unknown change." }, { "date": "2026-03-06T18:35:43.406018Z", "number": "13", "summary": "References created (1)." }, { "date": "2026-03-20T09:36:35.135733Z", "number": "14", "summary": "Source connected.| CVE status created. (valid)| EPSS created." } ], "status": "interim", "version": "14" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/4.4.0", "product": { "name": "vers:unknown/4.4.0", "product_id": "CSAFPID-5760074", "product_identification_helper": { "purl": "pkg:pypi/irrd@4.4.0" } } }, { "category": "product_version_range", "name": "vers:unknown/4.4.1", "product": { "name": "vers:unknown/4.4.1", "product_id": "CSAFPID-5760075", "product_identification_helper": { "purl": "pkg:pypi/irrd@4.4.1" } } }, { "category": "product_version_range", "name": "vers:unknown/4.4.2", "product": { "name": "vers:unknown/4.4.2", "product_id": "CSAFPID-5760076", "product_identification_helper": { "purl": "pkg:pypi/irrd@4.4.2" } } }, { "category": "product_version_range", "name": "vers:unknown/4.4.3", "product": { "name": "vers:unknown/4.4.3", "product_id": "CSAFPID-5760077", "product_identification_helper": { "purl": "pkg:pypi/irrd@4.4.3" } } }, { "category": "product_version_range", "name": "vers:unknown/4.4.4", "product": { "name": "vers:unknown/4.4.4", "product_id": "CSAFPID-5760078", "product_identification_helper": { "purl": "pkg:pypi/irrd@4.4.4" } } }, { "category": "product_version_range", "name": "vers:unknown/4.5.0", "product": { "name": "vers:unknown/4.5.0", "product_id": "CSAFPID-5760080", "product_identification_helper": { "purl": "pkg:pypi/irrd@4.5.0" } } }, { "category": "product_version_range", "name": "vers:unknown/>=4.4.0|<4.4.5", "product": { "name": "vers:unknown/>=4.4.0|<4.4.5", "product_id": "CSAFPID-5760079" } }, { "category": "product_version_range", "name": "vers:unknown/>=4.5.0|<4.5.1", "product": { "name": "vers:unknown/>=4.5.0|<4.5.1", "product_id": "CSAFPID-5760081" } } ], "category": "product_name", "name": "irrd" } ], "category": "vendor", "name": "irrdnet" } ] }, "vulnerabilities": [ { "cve": "CVE-2026-28681", "cwe": { "id": "CWE-601", "name": "URL Redirection to Untrusted Site ('Open Redirect')" }, "notes": [ { "category": "description", "text": "## 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.", "title": "github - https://github.com/advisories/GHSA-22m3-c7vp-49fj" }, { "category": "description", "text": "## 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.", "title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/PyPI%2FGHSA-22m3-c7vp-49fj.json?alt=media" }, { "category": "description", "text": "Internet Routing Registry daemon version 4 is an IRR database server, processing IRR objects in the RPSL format. From version 4.4.0 to before version 4.4.5 and from version 4.5.0 to before version 4.5.1, 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 has been patched in versions 4.4.5 and 4.5.1.", "title": "nvd - https://nvd.nist.gov/vuln/detail/CVE-2026-28681" }, { "category": "description", "text": "Internet Routing Registry daemon version 4 is an IRR database server, processing IRR objects in the RPSL format. From version 4.4.0 to before version 4.4.5 and from version 4.5.0 to before version 4.5.1, 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 has been patched in versions 4.4.5 and 4.5.1.", "title": "cveprojectv5 - https://www.cve.org/CVERecord?id=CVE-2026-28681" }, { "category": "other", "text": "0.0006", "title": "EPSS" }, { "category": "other", "text": "4.5", "title": "NCSC Score" }, { "category": "other", "text": "There is product data available from source Cveprojectv5, Is related to CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)", "title": "NCSC Score top increasing factors" }, { "category": "other", "text": "There is cwe data available from source Nvd", "title": "NCSC Score top decreasing factors" } ], "product_status": { "known_affected": [ "CSAFPID-5760074", "CSAFPID-5760075", "CSAFPID-5760076", "CSAFPID-5760077", "CSAFPID-5760078", "CSAFPID-5760079", "CSAFPID-5760080", "CSAFPID-5760081" ] }, "references": [ { "category": "external", "summary": "Source - github", "url": "https://github.com/advisories/GHSA-22m3-c7vp-49fj" }, { "category": "external", "summary": "Source raw - github", "url": "https://api.github.com/advisories/GHSA-22m3-c7vp-49fj" }, { "category": "external", "summary": "Source - osv", "url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/PyPI%2FGHSA-22m3-c7vp-49fj.json?alt=media" }, { "category": "external", "summary": "Source - nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-28681" }, { "category": "external", "summary": "Source raw - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-28681" }, { "category": "external", "summary": "Source - cveprojectv5", "url": "https://www.cve.org/CVERecord?id=CVE-2026-28681" }, { "category": "external", "summary": "Source raw - cveprojectv5", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/28xxx/CVE-2026-28681.json" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-28681" }, { "category": "external", "summary": "Source raw - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://github.com/irrdnet/irrd/security/advisories/GHSA-22m3-c7vp-49fj" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://github.com/irrdnet/irrd/commit/8408e0f1b9f47eb2f2e712d6153e32194df05fbb" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://github.com/irrdnet/irrd/commit/cf62df4a49d3891e80b2879d9b324d1af050000c" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://irrd.readthedocs.io/en/stable/releases/4.4.5" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://irrd.readthedocs.io/en/stable/releases/4.5.1" }, { "category": "external", "summary": "Reference - github", "url": "https://github.com/advisories/GHSA-22m3-c7vp-49fj" }, { "category": "external", "summary": "Reference - github; osv", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-28681" } ], "scores": [ { "cvss_v3": { "version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N", "baseScore": 8.1, "baseSeverity": "HIGH" }, "products": [ "CSAFPID-5760074", "CSAFPID-5760075", "CSAFPID-5760076", "CSAFPID-5760077", "CSAFPID-5760078", "CSAFPID-5760079", "CSAFPID-5760080", "CSAFPID-5760081" ] } ], "title": "CVE-2026-28681" } ] }