Comparison Overview
GRAV®
GRAV®
Austin, Texas, US, 78744
Last Update: 22/09/2026
21 years of age or older. A beloved brand from Austin, TX. GRAV wants to better understand and stand beside more of you, the community of smokers and advocates nationwide who support our way of life. We are deeply invested in the well-being of our colleagues, our custo...
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...
Compliance Ranges Comparison
GRAV®
BİM Birleşik Mağazalar A.Ş
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
GRAV® has 45.65% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for BİM Birleşik Mağazalar A.Ş in 2026.
Incident History - GRAV® (X = Date, Y = Severity)
GRAV® cyber incidents detection timeline including parent company and subsidiaries.
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.
Notable Incidents
GRAV®
BİM Birleşik Mağazalar A.Ş
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)