Comparison Overview
Middlesbrough Council

Middlesbrough Council
Civic Centre, Middlesbrough, TS1 9FY, GB
Last Update: 02/04/2026
Middlesbrough is a fantastic place, proud of its heritage and ambitious enough to shape an entirely different future. At Middlesbrough Council we have set our city-scale plans to deliver over £600 million of investment that will promote economic growth and strengthen ...

Belastingdienst
Korte Voorhout 7, Den Haag, NL, 2500 EE
Last Update: 03/04/2026
De organisatie bestaat uit diverse onderdelen, waaronder de Belastingdienst, Douane, Toeslagen, FIOD en enkele facilitaire organisaties. Met ruim 30.000 medewerkers werken we in kantoren die verspreid zijn over het hele land. Gezamenlijk heffen, innen en controleren we ...
Compliance Ranges Comparison

Middlesbrough Council







Belastingdienst






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Middlesbrough Council in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Belastingdienst in 2026.
Incident History - Middlesbrough Council (X = Date, Y = Severity)
Middlesbrough Council cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Belastingdienst (X = Date, Y = Severity)
Belastingdienst cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Middlesbrough Council

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