Comparison Overview
BBC Monitoring

BBC Monitoring
New Broadcasting House, Portland Place, London, Greater London, W1A 1AA, GB
Last Update: 05/02/2026
BBC Monitoring tracks, translates, analyses and summarises global media to help you make sense of world events. We have been capturing essential media insights for governments, NGOs, academia, corporates and intergovernmental organisations since 1939. Today, we thrive ...

Fox Corporation
New York, New York, US, 10036
Last Update: 27/07/2026
Under the FOX banner, we produce and distribute content through some of the world’s leading and most valued brands, including: FOX News Media, FOX Sports, FOX Entertainment, FOX Television Stations and Tubi Media Group. We empower a diverse range of creators to imagine ...
Compliance Ranges Comparison

BBC Monitoring







Fox Corporation






Benchmark & Cyber Underwriting Signals
Incidents vs Broadcast Media Production and Distribution Industry Avg (This Year)
No incidents recorded for BBC Monitoring in 2026.
Incidents vs Broadcast Media Production and Distribution Industry Avg (This Year)
No incidents recorded for Fox Corporation in 2026.
Incident History - BBC Monitoring (X = Date, Y = Severity)
BBC Monitoring cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fox Corporation (X = Date, Y = Severity)
Fox Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

BBC Monitoring

Fox Corporation
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.