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

CVE-2026-101278: OpenDMARC PSL Wildcard Handler RCE Vulnerability

CVE-2026-101278 is a remote code execution vulnerability in Trusted Domain Project OpenDMARC affecting the PSL Wildcard Handler component. This flaw allows remote attackers to exploit origin validation errors. This article covers technical details, affected versions, security impact, and available mitigation strategies.

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

CVE-2026-101278 is an origin validation error [CWE-345] in Trusted Domain Project OpenDMARC through version 1.4.2. The flaw resides in the opendmarc_get_tld function within libopendmarc/opendmarc_tld.c, part of the PSL (Public Suffix List) Wildcard Handler component. Improper handling of PSL wildcard rules causes OpenDMARC to compute an incorrect organizational domain when evaluating email authentication. A remote actor can leverage this to influence DMARC alignment decisions on affected mail flows. A public exploit description is available. The vendor did not respond to disclosure attempts.

Critical Impact

Incorrect organizational domain resolution can weaken DMARC alignment enforcement, enabling policy bypass scenarios that undermine email authentication decisions.

Affected Products

  • Trusted Domain Project OpenDMARC 1.4.2 and earlier
  • Mail servers and MTAs relying on OpenDMARC for DMARC evaluation
  • Downstream distributions packaging vulnerable OpenDMARC builds

Discovery Timeline

  • 2026-09-29 - CVE CVE-2026-101278 published to NVD
  • 2026-09-29 - Last updated in NVD database

Technical Details for CVE-2026-101278

Vulnerability Analysis

OpenDMARC uses the Public Suffix List to determine the organizational domain of a sender when performing DMARC alignment. The opendmarc_get_tld function walks PSL entries to identify where a registerable domain begins. The PSL format supports wildcard rules (for example, *.ck) and exception rules (!www.ck) that require specific matching precedence. The vulnerability stems from incorrect handling of wildcard entries during lookup. As a result, OpenDMARC can select the wrong organizational domain boundary for certain hostnames under wildcard suffixes.

Misaligned organizational domain calculation directly affects DMARC's alignment checks against SPF and DKIM identifiers. When the computed org domain does not match the true registerable boundary, a receiving MTA may accept or reject messages based on the wrong policy record. This weakens trust in DMARC verdicts for domains sitting under PSL wildcards.

Root Cause

The root cause is improper origin validation [CWE-345] in the PSL wildcard matching logic of opendmarc_get_tld. The function does not correctly apply wildcard precedence when resolving hostnames under multi-level public suffixes, yielding an incorrect organizational domain.

Attack Vector

Exploitation occurs over the network through crafted email envelopes whose sender domains fall under PSL wildcard suffixes. An attacker sends messages designed to trigger the flawed org-domain computation on a receiver running OpenDMARC. No user interaction is required. The impact is limited to integrity of DMARC decisions rather than code execution or data exposure. See the GitHub OpenDMARC Wildcard Analysis for a detailed walkthrough.

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-101278

Indicators of Compromise

  • Inbound mail from domains under PSL wildcard suffixes receiving DMARC verdicts inconsistent with published policies.
  • OpenDMARC log entries showing organizational domains that do not match the expected registerable boundary.
  • DMARC aggregate (RUA) reports with alignment results that conflict with sender-side records.

Detection Strategies

  • Compare OpenDMARC's computed org domain against an independent PSL parser for a sample of inbound mail.
  • Audit opendmarc.log for pass verdicts on messages that should fail alignment under wildcard suffixes.
  • Correlate DMARC failure reports (RUF) with local verdicts to identify divergence.

Monitoring Recommendations

  • Enable verbose OpenDMARC logging and forward events to a central analytics platform.
  • Alert on spikes of DMARC pass results for domains historically producing fail or none.
  • Track version inventory of OpenDMARC packages across mail infrastructure.

How to Mitigate CVE-2026-101278

Immediate Actions Required

  • Inventory all OpenDMARC deployments and confirm versions at or below 1.4.2.
  • Refresh the local Public Suffix List and validate wildcard entries used by OpenDMARC.
  • Increase scrutiny on inbound mail from sender domains under PSL wildcard suffixes.

Patch Information

No vendor patch is referenced in the published advisory. The vendor was contacted about the disclosure and did not respond. Monitor the VulDB entry for CVE-2026-101278 and the OpenDMARC project for updated releases.

Workarounds

  • Layer complementary DMARC evaluation using an independently maintained parser to cross-check verdicts.
  • Apply stricter local policies for senders whose organizational domain falls under PSL wildcards.
  • Restrict trust placed in DMARC-only decisions and pair with SPF and DKIM checks plus reputation scoring.
bash
# Configuration example: enable detailed OpenDMARC logging for verdict auditing
# /etc/opendmarc.conf
Syslog true
SyslogFacility mail
AuthservID HOSTNAME
SoftwareHeader true
HistoryFile /var/lib/opendmarc/opendmarc.dat
PublicSuffixList /usr/share/publicsuffix/public_suffix_list.dat

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.