Comparison Overview
Parfums Givenchy
Parfums Givenchy
77, Rue Anatole France, Levallois-Perret, 92300, FR
Last Update: 29/01/2026
Hubert de Givenchy’s storied ascent to famed couturier began in 1952, when he opened the doors to his eponymous Parisian couture house. When Givenchy met Audrey Hepburn, he fell for her irresistible charm and youthful spirit. She informed Givenchy’s singular vision o...
The Estée Lauder Companies Inc.
767 5th Ave, New York, NY, US, 10153
Last Update: 04/04/2026
The Estée Lauder Companies Inc. is one of the world’s leading manufacturers, marketers, and sellers of quality skin care, makeup, fragrance, and hair care products, and is a steward of outstanding luxury and prestige brands globally. The company’s products are sold in a...
Compliance Ranges Comparison
Parfums Givenchy
The Estée Lauder Companies Inc.
Benchmark & Cyber Underwriting Signals
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Parfums Givenchy in 2026.
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
The Estée Lauder Companies Inc. has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Parfums Givenchy (X = Date, Y = Severity)
Parfums Givenchy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The Estée Lauder Companies Inc. (X = Date, Y = Severity)
The Estée Lauder Companies Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Parfums Givenchy
The Estée Lauder Companies Inc.
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: *.*.