Comparison Overview
KENZO Parfums

KENZO Parfums
Paris, FR
Last Update: 11/03/2026
After leaving Japan in 1964, the young designer Kenzo Takada sailed for France and settled in Paris. By 1970 he had opened his first store and followed many years during which his Japanese and colorful style defied the fashion rules of his time. In 1988, he continued t...

Natura
Av. Alexandre Colares, 1.188, Vila Jaguara, São Paulo, São Paulo, BR, 05106-0000
Last Update: 16/09/2026
Founded in 1969, Natura is a Brazilian multinational in the cosmetics and personal care segment, a leader in direct sales in Brazil, and recognized for protecting the Amazon social biodiversity through its sustainable business model. Cruelty free. 100% vegan. With 7,000...
Compliance Ranges Comparison

KENZO Parfums







Natura






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

KENZO Parfums

Natura
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)