Comparison Overview
Giant Food
Giant Food
8301 Professional Place, Hyattsville, 20794, US
Last Update: 07/03/2026
At Giant Food, we are always striving to be better. A Better Place to Work, Better Place to Shop, and a Better Neighbor. From wellness and time-saving services, to serving our community and everything in between, we've been proudly serving you since '36.
Costa Coffee
1A Wimpole St, London, W1G 0EA, GB
Last Update: 13/09/2026
At Costa Coffee, we’ve been crafting with heart and changing the coffee game since 1971. Now part of The Coca-Cola Company, we proudly operate in over 50 countries, and we’re still growing! And we’re much more than our beloved stores. Consumers all over the world can no...
Compliance Ranges Comparison
Giant Food
Costa Coffee
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Giant Food in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Costa Coffee in 2026.
Incident History - Giant Food (X = Date, Y = Severity)
Giant Food cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Costa Coffee (X = Date, Y = Severity)
Costa Coffee cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Giant Food
Costa Coffee
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.