Comparison Overview
Euricom

Euricom
Blarenberglaan 3A, Mechelen, 2800, BE
Last Update: 03/12/2025
Sinds 1999 bouwen we bij Euricom software op maat die onze klanten vooruit helpt. Met meer dan 25 jaar ervaring in softwareontwikkeling, een sterke focus op .NET en JavaScript, en een team van experts die weten waar ze mee bezig zijn. We helpen bij elke fase van een s...

VOIS
London, GB
Last Update: 30/03/2026
VOIS (Vodafone Intelligent Solutions) is a strategic arm of Vodafone Group Plc, creating value for customers by delivering intelligent solutions through Talent, Technology & Transformation. As the largest shared services organisation in the global telco industry, our ...
Compliance Ranges Comparison

Euricom







VOIS






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

Euricom

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