Quick answers
- Is CVE-2026-53904 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53904 being exploited in the wild.
- How severe is CVE-2026-53904?
- Informational severity, with a CVSS score of 6.3, published 1 July 2026.
- Which products and versions are affected?
- MyComplianceOffice MCO 25.3.3.1.
- Is there a fix for CVE-2026-53904?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-53904 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-53904?
- Check whether you run MyComplianceOffice MCO at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The MCO application (confirmed in version 25.3.3.1) suffers from an improper restriction of excessive authentication attempts (CWE-307) and a weak password recovery mechanism (CWE-640). The password reset logic is designed such that initiating a reset request immediately invalidates the user's current password and any previously issued temporary passwords. Because there is no rate limiting on these requests, an attacker who knows a victim's email and can answer their security question can continuously trigger resets to keep the victim locked out. While security questions have a limited number of attempts, a successful guess allows for persistent account denial of service. No patch is currently confirmed as vendor contact attempts were unsuccessful.
Affected products
- MyComplianceOffice MCO 25.3.3.1
Timeline
- 2026-07-01: disclosed: Disclosed by CERT.PL after unsuccessful vendor contact attempts.
- 2026-07-01: advisory