Comparison Overview
Big Bazaar - Future Retail

Big Bazaar - Future Retail
9th Floor , Future Retail Limited , , Mumbai, Maharashtra, 400083, IN
Last Update: 13/11/2025
Big Bazaar is a household name that is used synonymously with ‘retail’ in India. We represent the requirements of a typical Indian home. Founded in 2001 by Kishore Biyani, we as a retail chain operate under the parent organisation – Future Group – that holds a significa...

Costco Wholesale
4401 4th Ave S, Seattle, 98134, US
Last Update: 12/07/2026
Costco Wholesale is a multibillion dollar global retailer with warehouse club operations in 14 countries. We are the recognized leader in our field, dedicated to quality in every area of our business and respected for our outstanding business ethics. Despite our large s...
Compliance Ranges Comparison

Big Bazaar - Future Retail







Costco Wholesale






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Big Bazaar - Future Retail in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Costco Wholesale in 2026.
Incident History - Big Bazaar - Future Retail (X = Date, Y = Severity)
Big Bazaar - Future Retail cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Costco Wholesale (X = Date, Y = Severity)
Costco Wholesale cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Big Bazaar - Future Retail

Costco Wholesale
FAQ
Latest Global CVEs
The GOOSE subscriber component improperly validates the UTC timestamp field in unauthenticated IEC 61850 GOOSE (EtherType 0x88B8) Layer-2 multicast messages. A specially crafted GOOSE frame containing an undersized timestamp field can trigger a heap out-of-bounds read during message processing, causing the process to crash and resulting in a denial-of-service condition.
OpenClaw Dashboard contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to execute arbitrary JavaScript in the administrator's browser session by injecting HTML markup into agent transcript messages processed through the sessions API. Attackers can craft a message containing inline event handler payloads such as an img tag with an onerror attribute within the 60-character rendering budget, which is stored in the session transcript and interpolated unsanitized into innerHTML on the default landing page, allowing theft of session tokens and unauthorized calls to authenticated administrative endpoints including agent instruction file modification.
MeshCentral 1.1.21 contains a cross-site WebSocket hijacking protection bypass vulnerability that allows unauthenticated remote attackers to hijack authenticated administrator sessions by exploiting an unconditional early return in the CheckWebServerOriginName() function within webserver.js when self-signed certificates are in use. Attackers can open cross-origin WebSocket connections to any of the twelve WebSocket endpoints, send crafted action commands to exfiltrate the server sessionKey used to sign session cookies, forge session tokens as arbitrary users, and gain full remote control of all managed devices governed by the MeshCentral instance.
The GOOSE parser contains an off-by-one boundary-handling flaw that can be triggered by a single unauthenticated Layer-2 multicast frame on the process bus. When specific GOOSE message fields are processed, the parser advances its internal buffer position incorrectly, resulting in a heap out-of-bounds read. On affected platforms, this condition reliably terminates the subscriber process and causes a denial-of-service.
The GOOSE payload parser contains a boundary handling flaw that can be triggered by a single unauthenticated Layer 2 multicast frame on the process bus. When processing specific payload fields, an attacker controlled inner element length may exceed its enclosing length, causing the parser to over read by one byte. This out-of-bounds read reliably terminates the subscriber process, resulting in a denial-of-service condition.