Skip to main content

OpenDKIM EUVDEUVD-2026-88052

| CVE-2026-100888 MEDIUM
Out-of-bounds Write (CWE-787)
2026-09-27 VulDB GHSA-wm7g-7hm5-7hfr
5.5
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Send email with crafted DKIM-Signature h= tag
  2. Delivery
    OpenDKIM milter parses signed-headers during canonicalization
  3. Exploit
    Trigger out-of-bounds write in dkim_canon_selecthdrs
  4. Execution
    Corrupt milter process memory
  5. Impact
    Crash mail filtering or corrupt state

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires OpenDKIM (<=2.11.0) deployed as a DKIM milter that verifies/processes inbound mail, so the attacker-controlled DKIM-Signature header - specifically the h= signed-headers tag - reaches dkim_canon_selecthdrs during canonicalization. No authentication, no user interaction, and default milter configurations that verify inbound signatures are affected; the practical limiting factor is that OpenDKIM must be in the mail path performing DKIM canonicalization on received messages, and the primary demonstrated impact is memory corruption (likely milter crash / mail-flow DoS) rather than confirmed code execution.

Impact

This is a CWE-787 out-of-bounds write in OpenDKIM's dkim_canon_selecthdrs header-selection routine, reachable remotely and unauthenticated (CVSS 4.0 AV:N/AC:L/PR:N/UI:N) because a DKIM milter processes attacker-controlled inbound DKIM-Signature headers, including the h= tag that drives header canonicalization. The vendor CVSS 4.0 of 6.9 rates all impacts Low (VC/VI/VA:L), which arguably understates a memory-corruption primitive - an OOB write can plausibly cause milter crashes (mail-flow DoS) and, depending on heap layout, more serious corruption. Publicly available exploit code exists (weitongli write-up), but there is NO EPSS score and NO CISA KEV listing, so there is no evidence of active or widespread exploitation - treat POC availability and active exploitation as distinct signals. The E:P (Proof-of-Concept) exploit maturity in the vector is consistent with 'POC exists, not weaponized.' The most important limiting factor is that OpenDKIM is effectively unmaintained (2.11.0 is the last release, ~2015) and the vendor did not respond to disclosure, so no official patch is expected - defenders relying on distro backports or migration to alternatives (e.g., rspamd) should plan accordingly. Net: a genuine, remotely-reachable memory-safety bug in mail infrastructure that merits attention, but current real-world exploitation risk is moderate rather than urgent absent KEV/EPSS signals.

Exploit ScenarioDerived

An attacker sends an email to a mail server running OpenDKIM as a verification milter, embedding a crafted DKIM-Signature header whose h= (signed-headers) tag is manipulated to drive an out-of-bounds write during header canonicalization/selection. No authentication or user interaction is required since inbound mail is processed automatically. Public proof-of-concept exploit code exists demonstrating the OOB write, most reliably resulting in a crash of the milter (mail-flow disruption).

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 28, 2026

Out-of-bounds write in Trusted Domain Project OpenDKIM through 2.11.0 allows remote, unauthenticated attackers to corrupt memory by sending a crafted DKIM-Signature header whose h= signed-headers tag is manipulated before it reaches dkim_canon_selecthdrs during canonicalization. The practical impact is expected to be a milter crash or mail-flow denial of service, with confirmed memory corruption rather than proven code execution, and the independent assessment maps it to CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L while the supplied CVSS 4.0 vector is AV:N/AC:L/AT:N/PR:N/UI:N. Publicly available exploit code exists for this issue, and no vendor-released patch was identified at time of analysis; the vendor was contacted and reportedly did not respond.

RemediationAI

No vendor-released patch was identified at time of analysis, and the vendor did not respond to the disclosure, so remediation must rely on compensating controls until an official fix is published. The most direct control is to temporarily suspend inbound DKIM verification or remove OpenDKIM from the inbound mail path if it is deployed as a verifying milter; the trade-off is loss of DKIM authentication for inbound messages, possible deliverability or policy impact, and potentially disabled spam/phishing checks that depend on DKIM results. A narrower mitigation is to reject, quarantine, or normalize inbound messages containing malformed or oversized h= tags at the SMTP edge using an SMTP proxy or a custom milter ahead of OpenDKIM; this can reduce exposure but may reject legitimate mail with unusual signed-header lists and requires careful tuning to avoid false positives. Restricting inbound SMTP access to trusted relays or gateways reduces the attacker population but is not always feasible for internet-facing MX hosts, and running the milter under process supervision with restart and resource limits only limits the blast radius of a crash; it does not prevent the out-of-bounds write. Monitor the VulDB advisory and CTI entry at https://vuldb.com/vuln/410837 and https://vuldb.com/vuln/410837/cti for updated vendor guidance or a patched release.

Affected VersionsENISA

OpenDKIM 2.2
OpenDKIM 2.6
OpenDKIM 2.7
OpenDKIM 2.11.0
OpenDKIM 2.9
OpenDKIM 2.5
OpenDKIM 2.3
OpenDKIM 2.0
OpenDKIM 2.1
OpenDKIM 2.10
OpenDKIM 2.4
OpenDKIM 2.8

Affected Packages

euvd opendkim no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

OpenDKIM is a DKIM milter that signs and verifies DomainKeys Identified Mail signatures in mail flow. DKIM signatures include an h= tag that lists the header fields covered by the signature, and that tag is parsed during canonicalization in libopendkim/dkim-canon.c. CVE-2026-100888 is a CWE-787 out-of-bounds write in dkim_canon_selecthdrs: manipulating the h argument causes the header-selection routine to write outside the intended buffer, which can corrupt memory in the milter process. The attack is reachable over the network because a remote sender can place attacker-controlled content in the DKIM-Signature header of an inbound message, and the CVSS 4.0 vector and independent assessment both indicate no privileges or user interaction are required. The affected CPE entry, cpe:2.3:a:trusted_domain_project:opendkim:*:*:*:*:*:*:*:*, identifies the Trusted Domain Project OpenDKIM package family as affected, with the description scoping the issue to versions up to 2.11.0.

Know when Opendkim gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 5.5 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
vuln.today AI 7.3 HIGH

Inbound mail reaches the milter with no auth or interaction (AV:N/AC:L/PR:N/UI:N); an OOB write most reliably yields availability/integrity impact with limited confidentiality, all Low absent proven RCE.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
SUSE HIGH

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
CVSS changed
Sep 28, 2026 - 00:22 NVD
6.9 (MEDIUM) 5.5 (MEDIUM)
CVE Published
Sep 27, 2026 - 23:30 cve.org
MEDIUM 6.9

DescriptionCVE.org

A weakness has been identified in Trusted Domain Project OpenDKIM up to 2.11.0. This affects the function dkim_canon_selecthdrs of the file libopendkim/dkim-canon.c of the component DKIM Signature Header Selection. Executing a manipulation of the argument h can lead to out-of-bounds write. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Threat Intelligence Overview

EPSS Score
0.3%
Top 80% exploitable
Prevalence
Medium
widely-used open-source DKIM milter for Postfix/Sendmail, but now unmaintained
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment Vendor VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Vendor StatusVendor

SUSE

Severity: Important

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy