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...

Coty
Buitenveldertselaan 3-5, Amsterdam, 1082, NL
Last Update: 15/09/2026
Since 1904, Coty has fearlessly pioneered innovation across the beauty industry. We have a reputation for breaking new ground; a history of ‘firsts’ and ‘bests’ that has laid the foundation for the industry as we know it today. For over a century, our brands have been ...
Compliance Ranges Comparison

Parfums Givenchy







Coty






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)
No incidents recorded for Coty in 2026.
Incident History - Parfums Givenchy (X = Date, Y = Severity)
Parfums Givenchy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Coty (X = Date, Y = Severity)
Coty cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Parfums Givenchy

Coty
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)