Mailpit has a Server-Side Request Forgery (SSRF) via HTML Check API
CVE-2026-23845GHSA-6jxm-fv7w-rw5j
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/axllent/mailpit 1.28.3), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 1.28.3
- Fixed in
- 1.28.3
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-6jxm-fv7w-rw5j lists affected ranges: Go github.com/axllent/mailpit >=0 <1.28.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
- EPSS
- CVE-2026-23845: 0.43% estimated exploitation activity in the next 30 days; percentile 37.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Server-Side Request Forgery (SSRF) via HTML Check CSS Download The HTML Check feature (/api/v1/message/{ID}/html-check) is designed to analyze HTML emails for compatibility. During this process, the inlineRemoteCSS() function automatically downloads CSS files from external <link rel="stylesheet" href="..." tags to inline them for testing. Affected Components - Primary File: internal/htmlcheck/css.go (lines 132-207) - API Endpoint: /api/v1/message/{ID}/html-check - Handler: server/apiv1/other.go (lines 38-75) - Vulnerable Functions: - inlineRemoteCSS() - line 132 - downloadToBytes() - line 193 - isURL() - line 221 Technical Details 1. Insufficient URL Validation (isURL() function): 2. Unrestricted Download (downloadToBytes() function): 3. Automatic CSS Processing: Attack Vectors Attack Vector 1: Cloud Metadata Credential Theft Attacker sends HTML email with: When HTML check is triggered: 1. Mailpit makes GET request to AWS metadata endpoint 2. Downloads IAM credentials as "CSS…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-6jxm-fv7w-rw5j
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-23845 Advisory: Mailpit has a Server-Side Request Forgery (SSRF) via HTML Check API IDs: CVE-2026-23845, GHSA-6jxm-fv7w-rw5j Record: https://patchnext.com/advisories/cve-2026-23845 (revision 1, source checked 26 Oct 2026, 15:14 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/axllent/mailpit 1.28.3. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/axllent/mailpit: affected < 1.28.3; fixed in 1.28.3 ## Suggested inspection (read-only) - Go github.com/axllent/mailpit: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/axllent/mailpit. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-6jxm-fv7w-rw5j (GitHub-reviewed advisory GHSA-6jxm-fv7w-rw5j lists affected ranges: Go github.com/axllent/mailpit >=0 <1.28.3) Commands are suggestions: review each one before running it.
Loading voting…