Comparison Overview
VASS

VASS
Avda. de Europa, 1, Alcobendas, Madrid, 28108, ES
Last Update: 09/12/2025
We are a global digital transformation company that puts organizations at the forefront of innovation, by bringing together talent, knowledge and technology. With our digital solutions, we lead people and organizations around the world on their transition towards the ...

EPAM Systems
41 University Drive Suite 202, Newtown, PA, US, 18940
Last Update: 05/04/2026
Since 1993, EPAM Systems, Inc. (NYSE: EPAM) has used its software engineering expertise to become a leading global provider of digital engineering, cloud and AI-enabled transformation services, and a leading business and experience consulting partner for global enterpri...
Compliance Ranges Comparison

VASS







EPAM Systems






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

VASS

EPAM Systems
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.