Comparison Overview
PERCASSI
PERCASSI
Via Paglia 1/D, Bergamo, 24122, IT
Last Update: 19/03/2026
Percassi is a solid entrepreneurial group capable of anticipating market trends by looking beyond the Italian borders. Its activities are mainly concentrated in three business areas: Retail, Real Estate and Atalanta Bergamasca Calcio. The Retail business develops and ma...
Marks and Spencer
Waterside House, London, W2 1NW, GB
Last Update: 30/06/2026
At M&S, we're dedicated to being the most trusted retailer, prioritising quality and delivering value. Every day, we bring the magic of M&S to our customers, whenever, wherever and however they want to shop with us. For over a century, we've set the standard, doing the ...
Compliance Ranges Comparison
PERCASSI
Marks and Spencer
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for PERCASSI in 2026.
Incidents vs Retail Industry Avg (This Year)
Marks and Spencer has 371.7% more incidents than the average of all companies with at least one recorded incident.
Incident History - PERCASSI (X = Date, Y = Severity)
PERCASSI cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Marks and Spencer (X = Date, Y = Severity)
Marks and Spencer cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
PERCASSI
Marks and Spencer
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: *.*.