Comparison Overview
Koninklijke Gazelle

Koninklijke Gazelle
Wilhelminaweg 8, Dieren, Gelderland, 6951 BP, NL
Last Update: 30/04/2026
Al meer dan 130 jaar zijn we als Koninklijke Gazelle een toonaangevend fietsenmerk in Nederland. We koesteren onze rijke geschiedenis en vakmanschap, maar altijd met de blik op een duurzame toekomst. De liefde voor de fiets, de fietser en de wereld om ons heen vind je t...

Bajaj Auto Ltd
Bajaj Auto Ltd, Mumbai - Pune Road, Akurdi, Pune, Maharashtra, IN, 411035
Last Update: 14/09/2026
A journey that began 75 years ago in a corner of India and has since traversed the world over. Uniting people from across countries, cultures, and customs over the years with a multitude of different dreams, there's power in an idea. An idea that gave rise to brands tha...
Compliance Ranges Comparison

Koninklijke Gazelle







Bajaj Auto Ltd






Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Koninklijke Gazelle in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
Bajaj Auto Ltd has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Koninklijke Gazelle (X = Date, Y = Severity)
Koninklijke Gazelle cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bajaj Auto Ltd (X = Date, Y = Severity)
Bajaj Auto Ltd cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Koninklijke Gazelle

Bajaj Auto Ltd
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)