Comparison Overview
ПАТ "СК "УСГ"

ПАТ "СК "УСГ"
вул. Івана Федорова, буд. 32-А, Київ, 03038, UA
Last Update: 19/04/2026
СК «УСГ» – сучасна та динамічна страхова компанія національного масштабу зі 100% іноземним капіталом. З лютого 2008 року СК «УСГ» є повноправним членом родини всесвітньовідомої Vienna Insurance Group – лідера страхового ринку Центральної та Східної Європи. Це зробило к...

Aflac
1932 Wynnton Rd, Columbus, 31999, US
Last Update: 13/08/2026
Over 50 Million people worldwide have chosen Aflac because of our commitment to providing customers with the confidence that comes from knowing they have assistance in being prepared for whatever life may bring. With Aflac, whether you're a large business or a small o...
Compliance Ranges Comparison

ПАТ "СК "УСГ"







Aflac






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for ПАТ "СК "УСГ" in 2026.
Incidents vs Insurance Industry Avg (This Year)
Aflac has 191.26% more incidents than the average of all companies with at least one recorded incident.
Incident History - ПАТ "СК "УСГ" (X = Date, Y = Severity)
ПАТ "СК "УСГ" cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aflac (X = Date, Y = Severity)
Aflac cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ПАТ "СК "УСГ"

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