# CVE-2026-84697: Mailpit SSRF Deny List Bypass via Azure Metadata and IPv6 Prefix

> Attackers can bypass IP deny lists to perform server-side request forgery, accessing internal resources via Azure metadata or IPv6 prefixes.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-qx8f-9cjx-54j9

## What is CVE-2026-84697?

CVE-2026-84697 is a medium-severity server-side request forgery vulnerability in axllent mailpit, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mailpit's IsInternalIP deny list function fails to block the Azure WireServer address 168.63.129.16 and the RFC 2765/6145 IPv4-translated IPv6 prefix, allowing server-side request forgery to internal destinations. Attackers can supply hostnames resolving to these addresses in message content to reach the link check API and proxy endpoint for accessing internal resources.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-84697?


## How do I fix CVE-2026-84697?

No fix has been published for CVE-2026-84697 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-84697 being exploited?

There is no known exploitation of CVE-2026-84697 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84697 and fix it if it is affected.

What it is: CVE-2026-84697 is a medium-severity server-side request forgery vulnerability in axllent mailpit, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84697 in the wild and no public exploit code.

Affected product: axllent mailpit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84697/ (Markdown: https://insights.sbomify.com/CVE-2026-84697/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84697
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84697
- OSV: https://osv.dev/vulnerability/CVE-2026-84697

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84697/
Summaries are generated and may contain mistakes; the official description above is the record.