Authentication bypass via static authentication cache keys
Published Oct 31, 2025 · Updated Oct 31, 2025
Authentication cache corruption in OX Dovecot Pro core 2.4.0 allows remote attackers to access the first cached user's account. The auth passdb and userdb drivers use the obsolete %u expansion as an effectively static cache key, so one user's lookup overwrites entries for other users. Exploitation requires authentication caching with an affected oauth2, PAM, BSD auth, or passwd driver; subsequent logins are resolved as the first cached user.
Summary
What happened
Authentication cache corruption in OX Dovecot Pro core 2.4.0 allows remote attackers to access the first cached user's account. The auth passdb and userdb drivers use the obsolete %u expansion as an effectively static cache key, so one user's lookup overwrites entries for other users. Exploitation requires authentication caching with an affected oauth2, PAM, BSD auth, or passwd driver; subsequent logins are resolved as the first cached user.
The record
- CVE
- CVE-2025-30189
- Published
- Oct 31, 2025
- Updated
- Oct 31, 2025
- Vendor
- Open-Xchange GmbH
- Product
- OX Dovecot Pro
- Classifications
- CWE-1250
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 31, 2025CVE publishedPublication date reported by the CVE source.
- Oct 31, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.4.0
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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