Comparison Overview
BİM Birleşik Mağazalar A.Ş
BİM Birleşik Mağazalar A.Ş
Abdurrahmangazi Mah.Ebubekir Cad. No:73 Sancaktepe, İstanbul, TR
Last Update: 06/09/2026
Türkiye’de perakende sektörünün lideri olan BİM Birleşik Mağazalar A.Ş., temel gıda ve tüketim malzemelerinin uygun fiyat ve yüksek kaliteyle tüketiciye ulaştırılması hedefiyle faaliyetlerine 1995 yılında 21 mağazayla başlamıştır. Yüksek indirim (hard-discount) modelini...
CarMax
12800 Tuckahoe Creek Parkway, Richmond, Virginia, US, 23238
Last Update: 14/09/2026
We're fueled by a common goal: creating an iconic car-buying experience. We make car-buying fair, accessible, and joyful for all. We are committed to making progress in how we positively impact our society, now and in the future. Above all, we care about people. We are ...
Compliance Ranges Comparison
BİM Birleşik Mağazalar A.Ş
CarMax
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for BİM Birleşik Mağazalar A.Ş in 2026.
Incidents vs Retail Industry Avg (This Year)
CarMax has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - BİM Birleşik Mağazalar A.Ş (X = Date, Y = Severity)
BİM Birleşik Mağazalar A.Ş cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CarMax (X = Date, Y = Severity)
CarMax cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BİM Birleşik Mağazalar A.Ş
CarMax
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)