Comparison Overview
Jean Paul GAULTIER
Jean Paul GAULTIER
325 rue Saint-Martin, PARIS, FR
Last Update: 07/02/2026
Fondée par son créateur éponyme en 1976, la maison Jean Paul Gaultier est un paradoxe parisien – mêlant les codes du style français à une rébellion iconoclaste, la qualité de la couture à une sensibilité urbaine, le choc au chic. Réputé pour son tailoring audacieux et...
Louis Vuitton
2 Rue du Pont Neuf, Paris, 75001, FR
Last Update: 19/06/2026
For more than 150 years, men and women at Louis Vuitton have shared the same spirit of excellence and passion, reaffirming their expertise every day, the world over. With us, every career is a journey, filled with excitement and challenge, desire and daring. There is no...
Compliance Ranges Comparison
Jean Paul GAULTIER
Louis Vuitton
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
No incidents recorded for Jean Paul GAULTIER in 2026.
Incidents vs Retail Luxury Goods and Jewelry Industry Avg (This Year)
Louis Vuitton has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Jean Paul GAULTIER (X = Date, Y = Severity)
Jean Paul GAULTIER cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Louis Vuitton (X = Date, Y = Severity)
Louis Vuitton cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Jean Paul GAULTIER
Louis Vuitton
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: *.*.