CVE-2026-15689
CRITICALDescription
Dancer2::Plugin::Auth::Extensible versions through 0.713 for Perl allow password reset link poisoning via the request Host header in _default_email_password_reset and _default_welcome_send. Both default emails emit a link of the form `$base/login/$code`, whose authority comes from the request Host header, or from X-Forwarded-Host under behind_proxy (obtained from Dancer2's request->base function). A POST to /login carrying submit_reset and a username needs no authentication: it stores a fresh reset code against that account and mails the account holder a link to a host of the sender's choosing. The welcome mail takes the same path when the application calls create_user with email_welcome set. Through 0.711 the handlers read `request->uri_base` and `request->base` directly; Versions 0.712 and later provide an uri_base configuration key that defaults to the untrusted `request->uri_base` when unset. The default configuration with reset_password_handler enabled and the default message text, a recipient who follows the link hands a working reset code to the sender's host, which is enough to take over the account.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Moderate risk: more likely to be exploited than 47% of all known CVEs.
References
Related Vulnerabilities
Other CWE-640 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-18818 | Critical | 9.8 | 98% | - | - |
| CVE-2023-7028 | Critical | 10.0 | 95% | KEV | Fix |
| CVE-2017-7615 | High | 8.8 | 91% | - | - |
| CVE-2024-2862 | Critical | 9.1 | 51% | - | - |
| CVE-2025-6216 | Critical | 9.8 | 35% | - | Fix |
| CVE-2019-19844 | Critical | 9.8 | 35% | - | Fix |
Common questions
How do I fix CVE-2026-15689?
No published fix for CVE-2026-15689 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-15689 being actively exploited?
Not that we know of. CVE-2026-15689 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.61% is the estimated probability that it will be exploited in the next 30 days. That is higher than 47% of all scored CVEs.
How severe is CVE-2026-15689?
CVE-2026-15689 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-15689
Markdown
[](https://tridentstack.com/cve/CVE-2026-15689)HTML
<a href="https://tridentstack.com/cve/CVE-2026-15689"><img src="https://tridentstack.com/cve/badge/CVE-2026-15689.svg" alt="CVE-2026-15689"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-26.