Comparison Overview
Hebe
Hebe
Józefa Piusa Dziekońskiego 1, Warszawa, Mazowieckie, 00-728, PL
Last Update: 03/11/2025
Wierzymy, że prawdziwe piękno wynika z postaw i wartości. Pragniemy być firmą, która w imię zdrowia i piękna wychodzi naprzeciw potrzebom kobiet i mężczyzn, dlatego, w ramach naszych codziennych działań, dbamy o: - INNOWACJE - rozwijamy organizację, produkty, stosowane...
Lidl GB
14 Kingston Rd, Chessington, Surbiton KT5 9NU, London, KT5 9NU, GB
Last Update: 10/07/2026
At Lidl, we’re a pretty close bunch. Sure, we all bring something unique to the table — but when you scratch below the surface, we’ve also got a whole lot in common. We’re plate spinners and problem solvers, working hard to keep homes stocked up across the UK. Just lik...
Compliance Ranges Comparison
Hebe
Lidl GB
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Hebe in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Lidl GB in 2026.
Incident History - Hebe (X = Date, Y = Severity)
Hebe cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lidl GB (X = Date, Y = Severity)
Lidl GB cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hebe
Lidl GB
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.