Service termination via unsynchronized proxy cache access
Published Jul 20, 2026 · Updated Jul 20, 2026
Race condition in Axllent Mailpit before 1.30.0 allows remote attackers to terminate the service through concurrent proxy requests. The screenshot and print proxy reads its package-level assets cache without assetsMutex while cleanup and CSS rewriting update the same map. An attacker needs unauthenticated HTTP access and the ability to place a CSS-linked message; exploitation exits the process and stops SMTP, POP3, and HTTP listeners.
Summary
What happened
Race condition in Axllent Mailpit before 1.30.0 allows remote attackers to terminate the service through concurrent proxy requests. The screenshot and print proxy reads its package-level assets cache without assetsMutex while cleanup and CSS rewriting update the same map. An attacker needs unauthenticated HTTP access and the ability to place a CSS-linked message; exploitation exits the process and stops SMTP, POP3, and HTTP listeners.
The record
- CVE
- CVE-2026-45712
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- Axllent
- Product
- Mailpit
- Classifications
- CWE-362, CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 20, 2026CVE publishedPublication date reported by the CVE source.
- Jul 20, 2026Record 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=< 1.30.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
- Concurrent proxy request proof of conceptproof 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