# CVE-2025-67896: Memory corruption in Exim

> Remote attackers can trigger a heap-based buffer overflow in Exim mail servers with specific rate-limit settings, potentially leading to code execution or service disruption.

- **Severity:** High 7.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Dec 2025
- **Updated:** 18 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-67896, GHSA-6qxw-x3vc-phrg

## What is CVE-2025-67896?

CVE-2025-67896 is a high-severity memory corruption vulnerability in Exim Exim, published on 14 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Exim before 4.99.1, with certain non-default rate-limit configurations, allows a remote heap-based buffer overflow because database records are cast directly to internal structures without validation.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-67896?

It affects 1 product.


Products: Exim Exim.

## How do I fix CVE-2025-67896?

Upgrade to a fixed version.

## Is CVE-2025-67896 being exploited?

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

## Other vulnerabilities in Exim Exim

- [CVE-2026-45185](https://insights.sbomify.com/CVE-2026-45185/): Use after free in Exim (critical 9.8)
- [CVE-2023-42115](https://insights.sbomify.com/CVE-2023-42115/): Exim AUTH Out-Of-Bounds Write Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2020-28017](https://insights.sbomify.com/CVE-2020-28017/): Integer overflow in n/a (critical 9.8)
- [CVE-2020-28018](https://insights.sbomify.com/CVE-2020-28018/): Use after free in n/a (critical 9.8)
- [CVE-2020-28020](https://insights.sbomify.com/CVE-2020-28020/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67896 and fix it if it is affected.

What it is: CVE-2025-67896 is a high-severity memory corruption vulnerability in Exim Exim, published on 14 Dec 2025. 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-2025-67896 in the wild and no public exploit code.

Affected product: Exim Exim. 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-2025-67896/ (Markdown: https://insights.sbomify.com/CVE-2025-67896/index.md)
```

## Sources

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

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