Comparison Overview
U.S. Embassy Madrid

U.S. Embassy Madrid
Calle de Serrano, 75, Madrid, 28006, ES
Last Update: 27/04/2026
La Embajada de Estados Unidos en Madrid representa al gobierno de Estados Unidos en España y Andorra. España es un aliado y amigo indispensable, nos unen valores comunes y profundos lazos históricos y culturales. Estados Unidos y España trabajan en estrecha colaboración...

European Commission
Rue de la loi, Brussels, 1049, BE
Last Update: 04/04/2026
The Commission represents and upholds the interests of the EU as a whole, and is independent of national governments. The European Commission prepares legislation for adoption by the Council (representing the member countries) and the Parliament (representing the citiz...
Compliance Ranges Comparison

U.S. Embassy Madrid







European Commission






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for U.S. Embassy Madrid in 2026.
Incidents vs Government Administration Industry Avg (This Year)
European Commission has 482.52% more incidents than the average of all companies with at least one recorded incident.
Incident History - U.S. Embassy Madrid (X = Date, Y = Severity)
U.S. Embassy Madrid cyber incidents detection timeline including parent company and subsidiaries.
Incident History - European Commission (X = Date, Y = Severity)
European Commission cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

U.S. Embassy Madrid

European Commission
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.