Comparison Overview
Bajaj Auto Ltd
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...
Mattel, Inc.
333 Continental Blvd, El Segundo, 90245, US
Last Update: 13/09/2026
We empower generations to explore the wonder of childhood and reach their full potential. We treat play as if the future depends on it — because it does. Play is our language, and we speak to our consumers authentically by representing the world as they see and imagine...
Compliance Ranges Comparison
Bajaj Auto Ltd
Mattel, Inc.
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
Bajaj Auto Ltd has 60.0% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Mattel, Inc. in 2026.
Incident History - Bajaj Auto Ltd (X = Date, Y = Severity)
Bajaj Auto Ltd cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mattel, Inc. (X = Date, Y = Severity)
Mattel, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Bajaj Auto Ltd
Mattel, Inc.
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)