Comparison Overview
vivo Europe

vivo Europe
Calle Orense, 58, Madrid, 28020, ES
Last Update: 20/01/2026
vivo is a global technology company that connects users to the digital world. vivo creates mobile products and services featuring life: inspired by how people live, inspiring them to feel more alive. Guided by our customers, vivo integrates technology and fashion in uni...

Eldorado LLC
Russia, Moscow, 125493, RU
Last Update: 01/04/2026
Eldorado is one of Russia's largest retailers of consumer electronics and household appliances. The company is present in almost all regions of Russia. Eldorado develops multichannel sales and operates over 600 stores throughout the country. Eldorado LLC is a pa...
Compliance Ranges Comparison

vivo Europe







Eldorado LLC






Benchmark & Cyber Underwriting Signals
Incidents vs Consumer Electronics Industry Avg (This Year)
No incidents recorded for vivo Europe in 2026.
Incidents vs Consumer Electronics Industry Avg (This Year)
No incidents recorded for Eldorado LLC in 2026.
Incident History - vivo Europe (X = Date, Y = Severity)
vivo Europe cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Eldorado LLC (X = Date, Y = Severity)
Eldorado LLC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

vivo Europe

Eldorado LLC
FAQ
Latest Global CVEs
PlaywrightCapture stored capture-specific configuration and runtime data as mutable class-level variables rather than instance-level variables. Consequently, multiple Capture objects running within the same Python process could share state, including HTTP headers, cookies, browser storage, HTTP credentials, proxy configuration, user-agent settings, geolocation information, and captured request data. In a multi-user or concurrent deployment, information supplied during one capture could therefore persist and be reused by a subsequent or parallel capture. This could result in the disclosure of authentication cookies, credentials, browser storage, or captured request data belonging to another user. It could also cause requests to be performed with another capture's authentication context, headers, or proxy configuration, potentially enabling unauthorized access to remote resources or interference with other capture operations. The vulnerability is resolved by initializing all capture-specific settings and request data as instance variables in the Capture constructor, ensuring that state is isolated between capture operations.
Anubis is a Web AI Firewall Utility that challenges users' connections in order to protect upstream resources from scraper bots. From 1.22.0 until 1.26.0-pre1, lib/policy/checker.go PathChecker.Check() trusted the client-controlled X-Original-URI header before matching r.URL.Path, allowing an HTTP client to match default data/common/keep-internet-working.yaml ALLOW rules such as ^/\.well-known/.*$ and bypass the Anubis challenge. This issue is fixed in version 1.26.0-pre1.
Wekan is open source kanban built with Meteor. Prior to 9.46, header-login with HEADER_LOGIN_TRUSTED_IPS uses getRequestIp() in server/lib/headerLoginAuth.js to trust the client-supplied X-Forwarded-For header before the real socket address, allowing an unauthenticated attacker to send HEADER_LOGIN_ID for any username and receive a meteor_login_token session, including for admin. This issue is fixed in version 9.46.
MaaAssistantArknights is a one-click tool for daily Arknights tasks. In the current dev-v2 workflow, .github/workflows/release-preparation.yml inlined attacker-controlled github.event.pull_request.title into a run: shell command during the pull_request opened, reopened, and ready_for_review events, so a non-draft fork PR whose title starts with Release v could execute shell commands on the ubuntu-latest runner during the generate-changelog job. This vulnerability is fixed by commit cafc3946059e6337d2089d4fec8b6885ba17c332.
Qinglong is a timed task management platform supporting Python3, JavaScript, Shell, and Typescript. Prior to 2.20.1, the init guard middleware in back/loaders/express.ts checks /api/user/init but not /open/user/init, while rewrite('/open/*', '/api/$1') rewrites the whitelisted /open/* path after JWT authentication and the guard have passed; an unauthenticated attacker can send PUT /open/user/init to reset administrator credentials on an initialized instance. This issue is fixed in 2.20.1.