Comparison Overview
U.S. Department of State – Bureau of Economic and Business Affairs

U.S. Department of State – Bureau of Economic and Business Affairs
Washington, DC, US
Last Update: 19/04/2026
This account was retired on 12/31/2025. Follow @Office of the Under Secretary for Economic Affairs (E) of the U.S. Department of State for updates.

UWV
La Guardiaweg 36 - 66, Amsterdam, 1043 DG, NL
Last Update: 03/04/2026
Bij UWV werken we aan een samenleving waarin iedereen mee kan doen. We helpen mensen op weg bij het vinden of behouden van werk. In geval van ziekte kijken we wat iemand nog wél kan. En als werken niet mogelijk is, zorgt UWV snel voor inkomen. We geven op deskundige en...
Compliance Ranges Comparison

U.S. Department of State – Bureau of Economic and Business Affairs







UWV






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for U.S. Department of State – Bureau of Economic and Business Affairs in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for UWV in 2026.
Incident History - U.S. Department of State – Bureau of Economic and Business Affairs (X = Date, Y = Severity)
U.S. Department of State – Bureau of Economic and Business Affairs cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UWV (X = Date, Y = Severity)
UWV cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

U.S. Department of State – Bureau of Economic and Business Affairs

UWV
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.