Comparison Overview
Elsevier | Research Intelligence

Elsevier | Research Intelligence
Radarweg 29, Amsterdam, 1043XN, NL
Last Update: 01/04/2026
Giving institutions momentum to make impact faster by delivering mission critical insights to impact makers with aim to advance human progress.

VINCI Energies
2169, Boulevard de la Défense, Nanterre, 92000, FR
Last Update: 31/03/2026
In a world undergoing constant change, VINCI Energies contributes to the environmental transition by helping bring about major trends in the digital landscape and energy sector. VINCI Energies’ teams roll out technologies and integrate customised multi-technical solutio...
Compliance Ranges Comparison

Elsevier | Research Intelligence







VINCI Energies






Benchmark & Cyber Underwriting Signals
Incidents vs Information Technology & Services Industry Avg (This Year)
No incidents recorded for Elsevier | Research Intelligence in 2026.
Incidents vs Information Technology & Services Industry Avg (This Year)
No incidents recorded for VINCI Energies in 2026.
Incident History - Elsevier | Research Intelligence (X = Date, Y = Severity)
Elsevier | Research Intelligence cyber incidents detection timeline including parent company and subsidiaries.
Incident History - VINCI Energies (X = Date, Y = Severity)
VINCI Energies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Elsevier | Research Intelligence

VINCI Energies
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.