Comparison Overview
Starbucks Korea

Starbucks Korea
중구 퇴계로 100 스테이트타워남산, 서울특별시, KR
Last Update: 01/03/2026
주식회사 에스씨케이컴퍼니는 1999년 이대 1호점을 시작으로 국내에 새로운 커피 문화를 소개하며, 국내 협력사와의 동반성장, 글로벌 인재 양성, 고용창출, 환경보호 등 다양한 이해관계자들과 지역사회를 배려하는 사회적 책임과 성장을 함께 추구하고 있습니다. 지역사회 속에서 일상을 풍요롭게 하는 특별한 스타벅스 경험을 전달하면서 업계를 선도하는 기업으로 성장해 오고 있습니다.

Red Bull
Am Brunnen 1, Fuschl, 5330, AT
Last Update: 01/04/2026
Red Bull Gives Wiiings to People and Ideas. This has driven us – and all we do – since 1987. Today, Red Bull operates in over 170 countries, selling more than 12 billion cans annually and growing! Above all, our people remain the essential ingredient in bringing the Red...
Compliance Ranges Comparison

Starbucks Korea







Red Bull






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

Starbucks Korea

Red Bull
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.