NotCVE-2026-0001
Descriptions
(1)
NotCVE
Cloudflare Universal SSL automatically adds additional CAA issue/issuewild records when a customer has Universal SSL enabled and publishes any CAA records for the zone; these auto-added records are not shown in the Cloudflare dashboard but are returned in DNS responses (e.g., via dig) and can include permissive authorizations such as CAA 0 issue "letsencrypt.org" and CAA 0 issuewild "letsencrypt.org".
When a domain owner uses RFC 8657 CAA extensions (e.g., accounturi and/or validationmethods) to restrict certificate issuance to a specific authorized ACME account and/or to limit validation methods, the presence of an additional auto-added CAA issue property without these RFC 8657 constraints can broaden authorization. Per RFC 8657, a CAA property without an accounturi parameter matches any account, and validationmethods only constrains authorization when present for a given property.
As a result, an attacker who can intercept and respond to CA domain-validation traffic (e.g., by gaining an on-path position through BGP route manipulation) may be able to complete DV validation at an otherwise authorized CA and obtain a publicly trusted certificate for the victim domain, enabling TLS man-in-the-middle attacks despite the domain owner’s attempt to enforce RFC 8657 account/method binding via CAA.
Attack scenario
Victim enables Cloudflare Universal SSL and publishes restrictive CAA records using RFC 8657 (accounturi and/or validationmethods) for the relevant CA (e.g., Let's Encrypt).
Cloudflare automatically adds additional permissive CAA records (not visible in the dashboard), including CAA 0 issue "letsencrypt.org" / CAA 0 issuewild "letsencrypt.org" without RFC 8657 constraints.
Attacker obtains an on-path interception position capable of observing/modifying CA validation traffic (e.g., via BGP route manipulation / traffic interception).
Attacker requests a DV certificate from the authorized CA for the victim domain using an attacker-controlled ACME account.
During CAA evaluation, the injected unparameterized issue "letsencrypt.org" can match any account (per RFC 8657), undermining the victim's intended accounturi binding; the injected record also lacks validationmethods constraints.
Attacker completes domain validation by intercepting and responding to the CA's validation requests, obtains a valid certificate, and uses it to perform TLS MITM against clients of the victim domain.
Timeline
(7)Vuln. Classification
(5)CVSS Scores
(1)SSVC
(1) NotCVE · 2026-01-19Threat Intelligence
2 resources · 2 sources NotCVE record — full content is public
Full Disclosure1
NotCVE1
Affected Vendors, Products & Versions
(1)|
NIST
NIST-compliant CPEs — NotCVE repairs & validates every CPE against the NIST 2.3 standard. repaired & validated by NotCVE vendor-original CPE |
Affected Configuration | Status |
|---|

Search CWE-693 in NotCVE