Comparison Overview
Valuno

Valuno
Luntmakargatan 18, Stockholm, Stockholm County, SE, 111 37
Last Update: 30/03/2026
At Valuno we're shaping the future of finance. Founded in 2016, we're a Swedish fintech company on a mission to make cryptocurrency an integral part of everyday life for individuals and businesses. Our roots are in payments, and we're driven by a clear vision: to make...

Aon
122 Leadenhall Street, London, GB, EC3V 4AN
Last Update: 26/07/2026
We exist to shape decisions for the better — to protect and enrich the lives of people around the world. Through actionable analytic insight, globally integrated Risk Capital and Human Capital expertise, and locally relevant solutions, our colleagues provide clients in ...
Compliance Ranges Comparison

Valuno







Aon






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

Valuno

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