Skip to content
Fencer Vulns
high 7.0

CVE-2026-94054 json

Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.

published 2026-09-19 50 d ago modified 2026-09-24 45 d ago also EUVD-2026-83612

cvss
7.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 19%
public exploits
0
none known

Summary

Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.

Patch / fix

  • Exim Exim 4.100.1
  • exim4 Debian 13 4.98.2-1+deb13u5
  • exim4 Debian 14 4.100.1-1

debian advisories DEBIAN-CVE-2026-94054

  • exim4 Ubuntu 22.04 LTS 4.95-4ubuntu2.12
  • exim4 Ubuntu 24.04 LTS 4.97-4ubuntu4.8
  • exim4 Ubuntu 26.04 LTS 4.99.1-1ubuntu1.5

ubuntu advisories UBUNTU-CVE-2026-94054

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

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-2026-94054 updated cvss 7.0

exim: Exim: Arbitrary code execution via attacker-controlled Proxy-Protocol

  • Red Hat All currently supported Red Hat products
    not 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
47 d ago

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 19% 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 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

  • Exim Exim

Classification

Weakness

References

Sources

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.