Comparison Overview
CalPERS

CalPERS
400 Q Street, Sacramento, 95811, US
Last Update: 01/04/2026
For nearly a century, CalPERS has built retirement and health security for state, school, and public agency members who invest their lifework in public service. Our pension fund serves more than 2 million members in the CalPERS retirement system and administers benefits...

UK Home Office
2 Marsham Street, London, GB, SW1P 4DF
Last Update: 30/04/2026
At the Home Office, we help to ensure that the country is safe and secure. We’ve been looking after UK citizens since 1782. We are responsible for: - working on the problems caused by illegal drug use - shaping the alcohol strategy, policy and licensing conditions - k...
Compliance Ranges Comparison

CalPERS







UK Home Office






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

CalPERS

UK Home Office
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.