Skip to main content
VulnerabilityPublished Updated

CVE-2025-54321: CVE-2025-54321 · Improper Control of Interaction Frequency

Affects CVE-2025-54321Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 8.6.9 as a priority.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.6.9
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade saykino/CVE-2025-54321 to 8.6.9.

Affected software

ProductAffectedFixed in
GitHubsaykino/CVE-2025-54321pkg:github/saykino/CVE-2025-54321Other threatsAffected
  • <8.6.9
Fixed in
  • 8.6.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should implement strict rate limiting on the password reset functionality to restrict the number of reset requests per user and per IP address within a defined time window. This can be achieved by configuring web application firewalls (WAFs) or modifying application logic to enforce throttling. Additionally, deploying CAPTCHA challenges on the reset password form can help prevent automated abuse. Monitoring and alerting on unusual spikes in password reset requests is essential to detect ongoing attacks early. Organizations should also ensure that users are educated to recognize legitimate password reset emails and report suspicious activity. Applying any available patches or updates from Ascertia promptly is critical once released. In the absence of patches, consider temporary workarounds such as disabling the reset password feature or restricting it to authenticated users only. Finally, reviewing email infrastructure capacity and filtering rules can help mitigate the impact of email flooding.

Description

In Ascertia SigningHub through 8.6.8, there is a lack of rate limiting on the reset password function, leading to an email bombing vulnerability. An authenticated attacker can exploit this by automating reset password requests.

References

Community reviews

Loading reviews…