EximApplication

CVE-2026-40687

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-30
Fix available
A fix is available. Upgrade to 4.99.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Exim before 4.99.2, when the SPA authentication driver is used with an adversarial SPA resource, there can be an out-of-bounds write that crashes the connection instance, or erroneous data processing that divulges data from uninitialized heap memory.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EximApplication
Affected:< 4.99.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.99.2 or later
Fixed in 4.99.2
Vendor patch code.exim.org →
Recommended fix High confidence

Exim 4.99.2 or later

  1. 1. Identify all Exim instances in the environment running versions prior to 4.99.2: exim -v 2>&1 | head -1 or exim --version
  2. 2. Obtain Exim 4.99.2 or later from the official Exim distribution (ftp.exim.org or your distribution's package repository)
  3. 3. Backup the current Exim configuration: cp -r /etc/exim /etc/exim.backup or equivalent
  4. 4. Install the upgraded Exim package using your system's package manager (apt-get install exim4, yum update exim, etc.) or compile from source if using source installation
  5. 5. Verify the new version is installed: exim -v 2>&1 | head -1
  6. 6. Validate Exim configuration syntax: exim -bV
  7. 7. Restart Exim service: systemctl restart exim or service exim restart
  8. 8. Test that SPA authentication functions correctly with the upgraded version
Caveat Review release notes for 4.99.2 to check for configuration or behavior changes; minor config syntax adjustments may be needed if the release introduced deprecations

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40687 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40687 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data