Comparison Overview
Nina Ricci
Nina Ricci
39, Avenue Montaigne, Paris, 75008, FR
Last Update: 22/01/2026
Since its creation in 1932, Nina Ricci has been a symbol of freedom and daring. Founded by Nina herself and her son Robert, the House encourages talents from all walks of life to work together to produce a powerful creative force, a way of enhancing all kinds of feminin...
Cartier
Route des Biches 10, Meyrin, CH, CH, 1217
Last Update: 01/04/2026
A reference in the world of luxury, Cartier, whose name is synonymous with open-mindedness and curiosity, stands out with its creations and finds beauty wherever it may lie. The Maison has several areas of expression. From jewelry to high jewelry, from watchmaking to f...
Compliance Ranges Comparison
Nina Ricci
Cartier
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Nina Ricci in 2026.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Cartier in 2026.
Incident History - Nina Ricci (X = Date, Y = Severity)
Nina Ricci cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cartier (X = Date, Y = Severity)
Cartier cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Nina Ricci
Cartier
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: *.*.