A long-standing security flaw in the MantisBT bug tracking software, identified as CVE-2017-7615, has been added to the VulnCheck Known Exploited Vulnerabilities (KEV) catalog. This development follows reports of active exploitation surfacing on November 3, 2026, more than nine years after the vulnerability was first disclosed.
The vulnerability, which centers on a flaw in the password recovery mechanism of MantisBT, was originally assigned a CVE identifier in April 2017. For nearly a decade, the issue remained a known but largely static entry in security databases. The recent inclusion in the VulnCheck catalog marks a significant shift in the risk profile for organizations still running legacy versions of the software.
Evidence of active exploitation was first documented on November 3, 2026. While the VulnCheck catalog now lists the vulnerability as actively exploited, it is important to note that this assessment is currently based on a single commercial research source. Other major vulnerability databases, including the CISA KEV catalog and the European Union’s ENISA repository, have not yet updated their records to reflect active exploitation of this specific flaw.
Because the claim of exploitation rests on a single source, the extent and nature of the attacks remain unverified by broader security agencies. The information provided by the VulnCheck catalog relies on public reports of exploitation activity, which have been aggregated for tracking purposes. There is currently no corroboration from other independent threat intelligence platforms or federal cybersecurity bodies to confirm the scale of these incidents.
The vulnerability itself dates back to the initial disclosure in April 2017. The time elapsed between the initial publication of the CVE and its recent listing as an exploited vulnerability is approximately 3,488 days, or roughly 9.6 years. This extended window highlights the potential for long-dormant vulnerabilities to become targets for attackers long after initial patches or mitigation strategies were first made available.
Organizations utilizing MantisBT should review their current installations to determine if they are running versions susceptible to the password recovery flaw. Because the vulnerability has now been flagged in a commercial KEV catalog, security teams should prioritize verifying their patch status, even if the software has been in use for many years without incident.
While the affected vendor has not issued a new statement regarding this specific update to the KEV catalog, the original 2017 disclosure provided the necessary technical details for administrators to secure their systems. Users are encouraged to cross-reference their software versions against the original CVE-2017-7615 records to ensure that all recommended updates have been applied.
As of mid-November 2026, the status of CVE-2017-7615 remains a point of focus for researchers monitoring the intersection of legacy software and modern threat activity. Security professionals should continue to monitor official channels and the broader vulnerability ecosystem for any further confirmation or additional data regarding the reported exploitation of this MantisBT flaw.




