CVE-2025-67896 json
Exim before 4.99.1, with certain non-default rate-limit configurations, allows a remote heap-based buffer overflow because database records…
published 2025-12-14 10 mo ago modified 2026-10-14 25 d ago also EUVD-2025-203281
- cvss
- 7.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-67896 updated cvss 8.2
exim: Exim: Remote heap corruption vulnerability
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 10 mo ago
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Exim Exim
Classification
- Weakness
-
- CWE-122 Heap-based Buffer Overflow
References
-
exim.org
/static/doc/security/
vendor-advisory
-
exim.org
/static/doc/security/EXIM-Security-2025-12-09.1/report.txt
vendor-advisory
-
openwall.com
/lists/oss-security/2025/12/11/2
mailing-list
-
openwall.com
/lists/oss-security/2025/12/14/1
mailing-list
-
openwall.com
/lists/oss-security/2025/12/18/3
mailing-list
Sources
- CVE List CVE-2025-67896
- NVD CVE-2025-67896
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.