Comparison Overview
PULL&BEAR

PULL&BEAR
Polígono Industrial Río do Pozo, NARÓN, A CORUÑA, ES, 15578
Last Update: 30/03/2026
Pull&Bear was founded in 1991 with a clear international vocation and the intention to sell clothes to young people committed to their environment who live in the community and interact together. Young people who choose to dress casually, rejecting stereotypes and wanti...

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...
Compliance Ranges Comparison

PULL&BEAR







Levi Strauss & Co.






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

PULL&BEAR

Levi Strauss & Co.
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)