Account lockout via unverified email reassignment
Published Sep 29, 2025 · Updated Sep 29, 2025
Improper access control in OpenML openml.org 2.0.20241110 and earlier allows remote authenticated users to lock out other users. The /profile email update accepts another account's existing email without ownership verification, reassigning the address and invalidating victim access. A lower-ID account and the victim's email address are required; the attack blocks login without exposing the victim's private data.
Summary
What happened
Improper access control in OpenML openml.org 2.0.20241110 and earlier allows remote authenticated users to lock out other users. The /profile email update accepts another account's existing email without ownership verification, reassigning the address and invalidating victim access. A lower-ID account and the victim's email address are required; the attack blocks login without exposing the victim's private data.
The record
- CVE
- CVE-2025-55795
- Published
- Sep 29, 2025
- Updated
- Sep 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284, CWE-639, T1531
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 29, 2025CVE publishedPublication date reported by the CVE source.
- Sep 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream account-lockout proof-of-concept stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo