Comparison Overview
Parfums Christian Dior

Parfums Christian Dior
190, Avenue Charles de Gaulle, Neuilly-sur-Seine, 92200, FR
Last Update: 29/03/2026
Christian Dior described himself as a fashion and perfume designer. The House of Dior, founded in 1946, changed the face of style forever when its New Look was unveiled in the halls of 30 Avenue Montaigne on February 12th, 1947. The revolutionary look was accompanied by...

L'Oréal
41, Rue Martre, Paris, FR, 92110
Last Update: 13/09/2026
No.1 Beauty Group Worldwide. No.1 most innovative company in Europe (Fortune's ranking). We are 90K employees across 150 countries on five continents, united by our shared purpose: creating the beauty that moves the world. Our 37 international brands are divided int...
Compliance Ranges Comparison

Parfums Christian Dior







L'Oréal






Benchmark & Cyber Underwriting Signals
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Parfums Christian Dior in 2026.
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for L'Oréal in 2026.
Incident History - Parfums Christian Dior (X = Date, Y = Severity)
Parfums Christian Dior cyber incidents detection timeline including parent company and subsidiaries.
Incident History - L'Oréal (X = Date, Y = Severity)
L'Oréal cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Parfums Christian Dior

L'Oréal
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout