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-101280 Overview
CVE-2026-101280 is an authentication bypass vulnerability in Trusted Domain Project OpenDMARC through version 1.4.2. The flaw resides in the opendmarc_policy_query_dmarc function within the Multi-Record Set Handler component. Attackers can manipulate DMARC records to bypass authentication checks through spoofing. The issue is classified under [CWE-287] Improper Authentication and can be exploited remotely without user interaction. Public exploit information is available, and the vendor did not respond to disclosure attempts.
Critical Impact
Remote attackers can downgrade DMARC policy enforcement by returning multiple DNS TXT records, enabling email spoofing against domains that rely on OpenDMARC for message authentication.
Affected Products
- Trusted Domain Project OpenDMARC versions up to and including 1.4.2
- Mail transfer agents integrating the OpenDMARC library for policy evaluation
- Email gateways relying on opendmarc_policy_query_dmarc for DMARC decisions
Discovery Timeline
- 2026-09-29 - CVE-2026-101280 published to the National Vulnerability Database
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-101280
Vulnerability Analysis
OpenDMARC is an open source implementation of Domain-based Message Authentication, Reporting, and Conformance (DMARC) used by mail servers to validate inbound email against publisher policies. The vulnerable function opendmarc_policy_query_dmarc handles DNS lookups for _dmarc TXT records and determines the resulting enforcement policy. When a domain publishes multiple TXT records at the _dmarc label, the multi-record set handler fails to reject or safely resolve the ambiguous response. An attacker who controls or influences the DNS response can supply a permissive record alongside a strict record, causing the library to select the weaker policy. The end result is authentication bypass by spoofing, allowing forged mail to pass DMARC evaluation.
Root Cause
The root cause is improper handling of multi-record TXT responses inside the DMARC policy query routine. RFC 7489 requires that domains with multiple DMARC records be treated as if no record were published, but the affected code path does not consistently enforce this rejection. This deviation from the specification lets adversaries downgrade or override policy semantics.
Attack Vector
Exploitation occurs over the network. An attacker publishes or injects multiple _dmarc TXT records for a targeted or attacker-controlled domain. When the receiving OpenDMARC-enabled mail server queries DNS, the parser selects a record that permits delivery instead of quarantining or rejecting the message. Detailed analysis is available in the GitHub OpenDMARC Analysis and the VulDB CVE-2026-101280 entry.
No verified proof-of-concept code is redistributed here. Refer to the linked advisories for reproduction details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-101280
Indicators of Compromise
- Inbound email that passes DMARC evaluation despite failing SPF and DKIM alignment for the claimed sending domain.
- DNS query responses to _dmarc.<domain> returning more than one TXT record containing v=DMARC1 tags.
- Mail server logs showing DMARC pass results for domains historically enforcing p=reject or p=quarantine.
Detection Strategies
- Compare DMARC evaluation outcomes recorded by OpenDMARC against independent authoritative DNS lookups of the same domain.
- Alert on domains that publish multiple DMARC TXT records, which violates RFC 7489 and may indicate abuse or misconfiguration.
- Correlate DMARC aggregate (RUA) reports across recipients to identify inconsistent policy enforcement.
Monitoring Recommendations
- Enable verbose OpenDMARC logging and forward events to a centralized SIEM for policy anomaly detection.
- Monitor DNS resolver telemetry for _dmarc responses that contain multiple valid records.
- Track authentication-results headers on delivered mail to spot unexpected dmarc=pass verdicts.
How to Mitigate CVE-2026-101280
Immediate Actions Required
- Inventory all mail transfer agents and gateways using the OpenDMARC library at version 1.4.2 or earlier.
- Restrict trust in DMARC verdicts for high-value domains until a patched build is deployed.
- Increase scrutiny on inbound mail from domains commonly targeted for spoofing, including finance and executive impersonation risks.
Patch Information
No vendor patch has been referenced in the published advisories. The Trusted Domain Project did not respond to disclosure attempts according to the VulDB Vulnerability #411037 record. Monitor the upstream OpenDMARC repository for future fixes and consider third-party maintained forks.
Workarounds
- Enforce SPF and DKIM alignment checks independently of the OpenDMARC library verdict for critical mail flows.
- Deploy a supplementary DMARC validator that explicitly rejects domains publishing multiple _dmarc TXT records.
- Route inbound mail through a hardened gateway that performs its own DNS resolution and policy evaluation.
- Consider disabling OpenDMARC-based enforcement and relying on alternative anti-spoofing controls until a fix is available.
# Configuration example: fail closed when multiple DMARC records are present
# Validate the _dmarc record set out-of-band before trusting OpenDMARC output
dig +short TXT _dmarc.example.com | grep -c 'v=DMARC1' \
| awk '{ if ($1 > 1) print "REJECT: multiple DMARC records detected"; else print "OK" }'
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

