Comparison Overview
Levi Strauss & Co.

Levi Strauss & Co.
1155 Battery St, San Francisco, US
Last Update: 05/09/2026
You’re an original. So are we. We’re a company of people who like to forge our own path. We invented the blue jean in 1873, and we reinvented khaki pants in 1986. We pioneered labor and environmental guidelines in manufacturing. And we work to build sustainability int...

C&A Brasil
Alameda Araguaia 1222, Barueri, BR
Last Update: 06/09/2026
A C&A foi fundada em 1841 pelos irmãos holandeses Clemens e August. Suas iniciais deram origem ao nome da marca. Somamos mais de 1,8 mil unidades em 24 países da Europa, América Latina e Ásia e estamos entre as maiores redes de varejo do mundo. No Brasil, tudo começou ...
Compliance Ranges Comparison

Levi Strauss & Co.







C&A Brasil






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
Levi Strauss & Co. has 58.51% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Apparel and Fashion Industry Avg (This Year)
No incidents recorded for C&A Brasil in 2026.
Incident History - Levi Strauss & Co. (X = Date, Y = Severity)
Levi Strauss & Co. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - C&A Brasil (X = Date, Y = Severity)
C&A Brasil cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Levi Strauss & Co.

C&A Brasil
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)