Exploitation observed; activity peaked at 3 mentions and remains active
Recommended action window: Immediate (within 24h)
NVD description
Description: To issue and renew TLS certificates on behalf of customers, Cloudflare's Universal SSL feature automatically manages the CAA RRset for the customer's zone. This auto-managed RRset is permissive by design (e.g. 'issue "letsencrypt.org"' without parameters). On Universal SSL zones, Cloudflare's authoritative DNS serves this auto-managed RRset at query time, superseding any customer-configured CAA records on the zone. When a customer publishes a stricter CAA record using the RFC 8657 accounturi or validationmethods parameters, the Certificate Authority does not observe those parameters when evaluating the served RRset under RFC 8659. As a result, the RFC 8657 account-binding and validation-method-binding protections are not enforced end-to-end on Universal SSL zones. Successful exploitation could result in issuance of a browser-trusted TLS certificate to an attacker, enabling MITM against the affected domain. Exploitation is non-trivial in practice: an attacker would need to hold an ACME account at one of the Certificate Authorities in the served CAA RRset and to simultaneously satisfy domain control validation across the multiple geographically distinct Network Perspectives the CA relies on for Multi-Perspective Issuance Corroboration. Cloudflare prefixes are anycast-announced from hundreds of locations globally, raising the bar against single-vantage-point BGP hijacks. Any resulting misissuance of a browser-trusted certificate is subject to Certificate Transparency logging required by major browsers, and would be visible to CT monitoring. Mitigation: Customers requiring strict RFC 8657 enforcement need to disable Universal SSL on the affected zone. Universal SSL's automatic CAA management and customer-set RFC 8657 accounturi and validationmethods enforcement are mutually exclusive by the nature of the issue, so there is no in-product workaround that preserves both. Certificate Transparency monitoring is recommended for all customers as a general detection control. Credits: David Osipov (ORCID: https://orcid.org/0009-0005-2713-9242), independent researcher
Priority
LOW
Exploitation
ACTIVE
PoC
NONE
Patch
NONE
Momentum
STABLE
| Date | Total | Labels |
|---|
| 2026-07-02 | 3 | General3 |
| 2026-07-21 | 1 | Active Exploitation1 |
CVE-2026-14440 Description: To issue and renew TLS certificates on behalf of customers, Cloudflare's Universal SSL feature automatically manages the CAA RRset for the customer's… https://www.cve.org/CVERecord?id=CVE-2026-14440
Post summary
The snippet simply links to the CVE record for CVE-2026-14440, with no additional technical details or actionable information.
Attention, elevated activities detected targeting Cloudflare Universal SSL (CVE-2026-14440) https://vuldb.com/vuln/375783/cti
Post summary
The post alerts on detected activity against Cloudflare Universal SSL CVE-2026-14440, indicating it is likely being actively exploited, but no PoC, exploit code, patch, or detailed technical information is supplied.
🚨*CVE* CVE-2026-14440 Description: To issue and renew TLS certificates on behalf of customers, Cloudflare's Universal SSL feature automatically manages the CAA RRset for the customer's… https://www.cve.org/CVERecord?id=CVE-2026-14440 ----- Traducción: CVE-2026-14440 Descri… http://infoflow.cloud`
Post summary
A brief reference to CVE-2026-14440 and a link to its record, describing Cloudflare’s Universal SSL updating CAA RRsets, without additional technical or exploitation details.
CVE-2026-14440 Cloudflare Universal SSL CAA Record Bypass Enables TLS Certificate Misis... https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-14440 Vulnerability Notification: https://alerts.vulmon.com/?utm_source=twitter&utm_medium=social&utm_campaign=2102281&utm_content=3
Post summary
A brief notification of CVE‑2026‑14440, mentioning a Cloudflare Universal SSL CAA record bypass vulnerability, but lacking detailed technical, exploit, patch, or activity information.