Comparison Overview
Fédération Wallonie-Bruxelles

Fédération Wallonie-Bruxelles
Boulevard Leopold II 44, Molenbeek-Saint-Jean, Brussels Region, 1080, BE
Last Update: 23/11/2025
La Fédération Wallonie-Bruxelles est une institution belge au service des francophones de Bruxelles et de Wallonie. Ses compétences s'exercent en matière d'Enseignement, de Culture, de Sport, de Jeunesse, de Recherche scientifique et de Maisons de justice, Elle dispose...

United States Postal Service
475 L’Enfant Plaza, S.W., Washington, D.C., US, 20260
Last Update: 02/08/2026
As the United States Postal Service continues its evolution as a forward-thinking, fast-acting company capable of providing quality products and services for its customers, it continues to remember and celebrate its roots as the first national network of communications ...
Compliance Ranges Comparison

Fédération Wallonie-Bruxelles







United States Postal Service






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Fédération Wallonie-Bruxelles in 2026.
Incidents vs Government Administration Industry Avg (This Year)
United States Postal Service has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Fédération Wallonie-Bruxelles (X = Date, Y = Severity)
Fédération Wallonie-Bruxelles cyber incidents detection timeline including parent company and subsidiaries.
Incident History - United States Postal Service (X = Date, Y = Severity)
United States Postal Service cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Fédération Wallonie-Bruxelles

United States Postal Service
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.