Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-101277 Overview
CVE-2026-101277 affects Trusted Domain Project OpenDKIM versions up to 2.11.0. The flaw resides in the dkim_process_set function within dkim.c, part of the Tag Tokenizer component. Manipulation of tag input causes the parser to rely on a less trusted source, weakening the trust decisions DKIM signatures are intended to enforce. The issue is classified under [CWE-348: Use of Less Trusted Source] and can be triggered remotely without authentication or user interaction. Public exploit material has been released. The maintainer was contacted prior to disclosure but did not respond.
Critical Impact
Remote attackers can influence DKIM tag parsing to affect signature validation trust decisions on mail servers running OpenDKIM through 2.11.0.
Affected Products
- Trusted Domain Project OpenDKIM versions up to and including 2.11.0
- Mail transfer agents integrating OpenDKIM as a milter (e.g., Postfix, Sendmail)
- Downstream Linux distributions packaging OpenDKIM ≤ 2.11.0
Discovery Timeline
- 2026-09-29 - CVE-2026-101277 published to the National Vulnerability Database (NVD)
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-101277
Vulnerability Analysis
OpenDKIM parses DomainKeys Identified Mail (DKIM) signatures by tokenizing tag-value pairs from message headers and DNS TXT records. The dkim_process_set function in dkim.c handles this tokenization for signature, key, and policy sets. The vulnerability causes the parser to accept or prefer data from a less trusted source during tag processing, weakening the trust boundary the DKIM standard defines. An attacker can craft a message or DNS response that manipulates how tags are parsed and attributed. This impacts signature integrity and availability of the verification result, but does not itself expose confidential data. Because DKIM outcomes drive downstream anti-spoofing decisions such as DMARC alignment, the flaw undermines email authentication guarantees.
Root Cause
The root cause is a parser design issue in dkim_process_set that treats attacker-influenced input as authoritative alongside trusted data. Under [CWE-348], the component fails to distinguish or prioritize the higher-integrity source when both are present during tag tokenization. This desync between parser expectations and actual input handling allows manipulation of the resulting tag set.
Attack Vector
Exploitation is network-based and requires no privileges or user interaction. An attacker sends a crafted email or serves a specially formed DNS response to influence the DKIM tag parser on the receiving OpenDKIM instance. The published proof of concept demonstrates a tag parser desync condition. Technical details are available in the GitHub PoC for OpenDKIM and the VulDB CVE-2026-101277 entry.
No verified code examples are available. Refer to the published PoC for the exact tag sequence that triggers the desync.
Stop Remote Code Execution Before It Runs
Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.
Stop Exploit AttemptsDetection Methods for CVE-2026-101277
Indicators of Compromise
- Unexpected d= or s= selector mismatches in OpenDKIM verification logs paired with pass results
- DKIM-Signature headers containing duplicated, malformed, or unusually ordered tag-value pairs
- Inbound messages whose DKIM verdict conflicts with DMARC alignment expectations from the claimed domain
Detection Strategies
- Compare OpenDKIM result= verdicts against independent verifiers such as dkimpy or a reference milter to surface parser divergence
- Alert on DKIM headers where tag keys repeat or contain non-canonical whitespace and encoding
- Correlate DKIM anomalies with sender reputation and DMARC failure telemetry to identify targeted abuse
Monitoring Recommendations
- Ingest OpenDKIM milter logs, MTA Authentication-Results headers, and DNS resolver logs into a central analytics platform
- Track version strings of deployed OpenDKIM binaries across mail infrastructure to identify unpatched hosts
- Monitor for spikes in DKIM-verified mail from newly observed domains that fail secondary reputation checks
How to Mitigate CVE-2026-101277
Immediate Actions Required
- Inventory all mail servers running OpenDKIM and identify versions at or below 2.11.0
- Restrict OpenDKIM milter exposure to trusted MTA sockets only and reject external connections at the network layer
- Increase scrutiny on DKIM pass verdicts by enforcing strict DMARC policies (p=reject or p=quarantine) for high-value domains
Patch Information
No vendor patch has been published at the time of NVD publication on 2026-09-29. The vendor did not respond to disclosure attempts. Monitor the Trusted Domain Project OpenDKIM repository and the VulDB Vulnerability #411034 entry for updates. Track your Linux distribution's security tracker for backported fixes.
Workarounds
- Evaluate migrating verification duties to an actively maintained alternative such as rspamd or dkimpy-milter until a patch is available
- Add pre-filter rules in the MTA to reject or quarantine messages with malformed DKIM-Signature headers (duplicate tags, invalid tag syntax)
- Enforce DMARC alignment checks downstream of OpenDKIM so a manipulated DKIM verdict cannot alone authorize a message
# Example Postfix milter restriction to loopback only
smtpd_milters = inet:127.0.0.1:8891
non_smtpd_milters = inet:127.0.0.1:8891
milter_default_action = tempfail
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

