Comparison Overview
La Maison du Chocolat
La Maison du Chocolat
225 Rue du Faubourg Saint-Honoré, Paris, 75008, FR
Last Update: 10/02/2026
For over three decades, passion, rigour and savoir-faire have been the driving force of the work, creation and excellence that is the taste of La Maison du Chocolat, founded in 1977 by Robert Linxe. From Parisian grand artisan to international luxury chocolatier, La M...
Best Buy
7601 Penn Ave South, Richfield, 55423-3645, US
Last Update: 04/04/2026
At Best Buy, our purpose is to enrich lives through technology. We do that by leveraging our unique combination of tech expertise and human touch to meet our customers’ everyday needs, whether they come to us online, visit our stores or invite us into their homes. With ...
Compliance Ranges Comparison
La Maison du Chocolat
Best Buy
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for La Maison du Chocolat in 2026.
Incidents vs Retail Industry Avg (This Year)
Best Buy has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - La Maison du Chocolat (X = Date, Y = Severity)
La Maison du Chocolat cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Best Buy (X = Date, Y = Severity)
Best Buy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
La Maison du Chocolat
Best Buy
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: *.*.