Comparison Overview
PUMA Group
PUMA Group
PUMA Way 1, Herzogenaurach, DE, 91074
Last Update: 04/04/2026
PUMA is one of the world’s leading sports brands, designing, developing, selling and marketing footwear, apparel and accessories. For more than 75 years, PUMA has relentlessly pushed sport and culture forward by creating fast products for the world’s fastest athletes. P...
Meijer
2929 Walker NW, Grand Rapids, 49544, US
Last Update: 28/03/2026
It takes guts to start a business during the Great Depression. And it takes vision to keep it going. Our founder, Hendrik Meijer, opened Thrifty Acres in 1934. Nearly thirty years later, his son, Fred, pioneered the world's first-ever supercenter, laying the groundwork...
Compliance Ranges Comparison
PUMA Group
Meijer
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for PUMA Group in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Meijer in 2026.
Incident History - PUMA Group (X = Date, Y = Severity)
PUMA Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Meijer (X = Date, Y = Severity)
Meijer cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PUMA Group
Meijer
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.