Skip to main content
Vulnerability Database/CVE-2026-101014

CVE-2026-101014: OpenDMARC DMARC Parser RCE Vulnerability

CVE-2026-101014 is a remote code execution vulnerability in Trusted Domain Project OpenDMARC up to version 1.4.2, affecting the DMARC Record Parser component. This post covers technical details, affected versions, and mitigation.

Published:

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-101014 Overview

CVE-2026-101014 is an off-by-one vulnerability in the Trusted Domain Project's OpenDMARC library, affecting versions up to 1.4.2. The flaw resides in the opendmarc_util_cleanup function within libopendmarc/opendmarc_util.c, which handles DMARC record parsing. An attacker can trigger the condition remotely by supplying crafted input that bypasses a boundary check using > instead of >=. A public exploit exists, increasing the likelihood of opportunistic attempts against mail infrastructure that depends on OpenDMARC for inbound message policy evaluation.

Critical Impact

Remote attackers can trigger an off-by-one condition in opendmarc_util_cleanup that may corrupt adjacent memory on mail servers performing DMARC validation.

Affected Products

  • Trusted Domain Project OpenDMARC versions up to and including 1.4.2
  • libopendmarc library, specifically the DMARC Record Parser component
  • Mail transfer agents and filter integrations that link against vulnerable libopendmarc builds

Discovery Timeline

  • 2026-09-28 - CVE-2026-101014 published to NVD
  • 2026-09-28 - Last updated in NVD database

Technical Details for CVE-2026-101014

Vulnerability Analysis

The vulnerability is classified under [CWE-189] as a numeric error producing an off-by-one condition. OpenDMARC's opendmarc_util_cleanup function validates an input string length against a destination buffer length before copying content. The original check permitted a string equal in length to the buffer, leaving no room for the terminating null byte. Processing a DMARC record of exactly buflen characters therefore writes one byte past the allocated region. Because OpenDMARC is typically invoked during inbound mail processing, the untrusted input originates from remote senders transmitting DMARC TXT records or related header material.

Root Cause

The root cause is an incorrect comparison operator in the input validation branch of opendmarc_util_cleanup. The pre-patch code rejected input when strlen((char *)str) > buflen, which still allowed strlen == buflen. That boundary case produces a one-byte overflow when the function writes the trailing null terminator.

Attack Vector

The attack vector is network-based with low complexity and requires no authentication or user interaction. An adversary who controls or influences DMARC records parsed by a target mail server can submit a payload sized precisely to the buffer boundary. The resulting single-byte write beyond the buffer may corrupt adjacent heap or stack metadata depending on the caller context.

c
{
 	char *sp, *ep;
 
-	if (str == NULL || buf == NULL || strlen((char *)str) > buflen)
+	if (str == NULL || buf == NULL || strlen((char *)str) >= buflen)
 	{
 		errno = EINVAL;
 		return NULL;

Source: GitHub OpenDMARC Commit b3b1da9. The patch replaces the strict greater-than comparison with greater-than-or-equal, reserving the final buffer position for the null terminator.

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 Attempts

Detection Methods for CVE-2026-101014

Indicators of Compromise

  • Unexpected crashes, segmentation faults, or errno=EINVAL returns from processes linking libopendmarc
  • DMARC TXT records in inbound mail logs whose length matches the configured parser buffer size exactly
  • Mail filter restarts or worker respawns correlated with inbound messages from a narrow set of sender domains

Detection Strategies

  • Inventory binaries that link against libopendmarc and compare versions against the fixed release containing commit b3b1da9264bc80324094a27c71e7369bdedc62ae.
  • Enable AddressSanitizer or equivalent heap canaries in non-production mail test environments to surface the one-byte write.
  • Hunt in mail gateway logs for anomalous DMARC record lengths and repeated parsing failures from the same sender infrastructure.

Monitoring Recommendations

  • Forward MTA, milter, and OpenDMARC daemon logs to a central analytics platform with alerting on crash signatures and abnormal restart counts.
  • Baseline normal DMARC record sizes per domain and alert on records that approach or match internal buffer limits.
  • Correlate inbound sender reputation with parser error rates to identify targeted probing of mail infrastructure.

How to Mitigate CVE-2026-101014

Immediate Actions Required

  • Apply the upstream OpenDMARC patch containing commit b3b1da9264bc80324094a27c71e7369bdedc62ae or rebuild from a release incorporating Pull Request #344.
  • Restart all services linked to libopendmarc after patching to ensure the updated library is loaded.
  • Audit distribution package versions and prioritize upgrades on mail gateways exposed to the public internet.

Patch Information

The fix is tracked in the Trusted Domain Project repository as commit b3b1da9264bc80324094a27c71e7369bdedc62ae, merged through Pull Request #344, which builds on the earlier work in Pull Request #188. Additional context is available via the VulDB entry for CVE-2026-101014 and the Weitongli analysis of the OpenDMARC cleanup off-by-one.

Workarounds

  • Where immediate patching is not possible, place inbound mail behind a filtering layer that rejects or truncates oversized DMARC TXT records before they reach OpenDMARC.
  • Run OpenDMARC under a dedicated low-privilege account and strict process isolation to limit the blast radius of any memory corruption.
  • Enable compiler hardening (-D_FORTIFY_SOURCE=2, stack canaries, ASLR) on packages that embed libopendmarc to reduce exploitability of the one-byte overflow.
bash
# Verify installed OpenDMARC version and locate linked binaries
opendmarc -V
ldconfig -p | grep libopendmarc
# Rebuild from patched source
git clone https://github.com/trusteddomainproject/OpenDMARC.git
cd OpenDMARC
git checkout b3b1da9264bc80324094a27c71e7369bdedc62ae
./configure && make && sudo make install
sudo systemctl restart opendmarc

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.