https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 11:24:23 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-332404 EUVD-2026-332404 https://cve.radiocsirt.org/vuln/euvd-2026-332404 https://cve.radiocsirt.org/vuln/fkie_cve-2026-14440 <p>Description:</p> <p>To issue and renew TLS certificates on behalf of customers, Cloudflare&#39;s Universal SSL feature automatically manages the CAA RRset for the customer&#39;s zone. This auto-managed RRset is permissive by design (e.g. &#39;issue &#34;letsencrypt.org&#34;&#39; without parameters). On Universal SSL zones, Cloudflare&#39;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.</p> <p>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 Tr…</p> <p>Description:</p> <p>To issue and renew TLS certificates on behalf of customers, Cloudflare&#39;s Universal SSL feature automatically manages the CAA RRset for the customer&#39;s zone. This auto-managed RRset is permissive by design (e.g. &#39;issue &#34;letsencrypt.org&#34;&#39; without parameters). On Universal SSL zones, Cloudflare&#39;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.</p> <p>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 Tr…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-14440 https://cve.radiocsirt.org/vuln/ghsa-vrv9-rjp4-w93c <p>Description:</p> <p>To issue and renew TLS certificates on behalf of customers, Cloudflare&#39;s Universal SSL feature automatically manages the CAA RRset for the customer&#39;s zone. This auto-managed RRset is permissive by design (e.g. &#39;issue &#34;letsencrypt.org&#34;&#39; without parameters). On Universal SSL zones, Cloudflare&#39;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.</p> <p>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 Tr…</p> <p>Description:</p> <p>To issue and renew TLS certificates on behalf of customers, Cloudflare&#39;s Universal SSL feature automatically manages the CAA RRset for the customer&#39;s zone. This auto-managed RRset is permissive by design (e.g. &#39;issue &#34;letsencrypt.org&#34;&#39; without parameters). On Universal SSL zones, Cloudflare&#39;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.</p> <p>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 Tr…</p> https://cve.radiocsirt.org/vuln/ghsa-vrv9-rjp4-w93c https://cve.radiocsirt.org/vuln/va-26-183-01 <p>Cloudflare Universal SSL adds Certification Authority Authorization (CAA) DNS records that override user-configured CAA records. The Universal SSL CAA records may be more permissive than user-configured records, for example, overriding the RFC 8657 &#39;accounturi&#39; parameter. An attacker with appropriate network access may be able to spoof domain validation and obtain a certificate for the target domain.</p> <p>Cloudflare Universal SSL adds Certification Authority Authorization (CAA) DNS records that override user-configured CAA records. The Universal SSL CAA records may be more permissive than user-configured records, for example, overriding the RFC 8657 &#39;accounturi&#39; parameter. An attacker with appropriate network access may be able to spoof domain validation and obtain a certificate for the target domain.</p> https://cve.radiocsirt.org/vuln/va-26-183-01