Axllent maintains Mailpit, a focused email testing and delivery platform where the durable signal centers on input-handling and protocol-interaction vulnerabilities such as server-side request forgery, CRLF injection, and improper control-sequence neutralization. The recurring weakness classes reflect the attack surface inherent to an email-interface tool that processes untrusted message content and manages HTTP and WebSocket interactions. Current severity, exploitation activity, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Axllent over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2026-23829MEDIUM Mailpit is an email testing tool and API for developers. Prior to version 1.28.3, Mailpit's SMTP server is vulnerable to Header Injection due to an insufficient Regular Expression | Jan 19, 2026 | 5.3 | 34 | NO | YES |
CVE-2026-21859MEDIUM Mailpit is an email testing tool and API for developers. Versions 1.28.0 and below have a Server-Side Request Forgery (SSRF) vulnerability in the /proxy endpoint, allowing attacker | Jan 8, 2026 | 5.3 | 31 | NO | YES |
CVE-2026-27808HIGH Mailpit is an email testing tool and API for developers. Prior to version 1.29.2, the Link Check API (/api/v1/message/{ID}/link-check) is vulnerable to Server-Side Request Forgery | Feb 26, 2026 | 8.6 | 28 | NO | NO |
CVE-2026-23845HIGH Mailpit is an email testing tool and API for developers. Versions prior to 1.28.3 are vulnerable to Server-Side Request Forgery (SSRF) via HTML Check CSS Download. The HTML Check f | Jan 19, 2026 | 7.5 | 26 | NO | NO |
CVE-2026-22689MEDIUM Mailpit is an email testing tool and API for developers. Prior to version 1.28.2, the Mailpit WebSocket server is configured to accept connections from any origin. This lack of Ori | Jan 10, 2026 | 6.5 | 23 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Axllent.
Media articles that mention a CVE ID that affects a product developed by Axllent — matched by CVE ID, not by vendor name.