Comparison Overview
ICM Japan![Mahindra and Mahindra Limited [Automotive and Farm Equipment Business]](https://images.rankiteo.com/companyimages/mahindraexperience.jpeg)
ICM Japan
Yokohama Kinko-Cho Bld 7F Kinko-cho 6-3, Kanagawa-ku, Yokohama, Yokohama, 221-0056, JP
Last Update: 02/01/2026
ICM JAPAN is the World-wide Used Vehicle Exporter of Quality Japanese Cars. Japanese Quality of the Used Car Market has always been the Top of the quality and Condition in the World. Here at ICM JAPAN, we are proud to supply you the gateway to the highest quality used c...
Mahindra and Mahindra Limited [Automotive and Farm Equipment Business]
Mahindra Towers, Akurli Road,, Mumbai, 400101, IN
Last Update: 20/05/2026
A USD 19.4 billion multinational group based in Mumbai, India, Mahindra provides employment opportunities to over 256,000 people across 100 countries. Mahindra operates in the key industries that drive economic growth, enjoying a leadership position in tractors, utility...
Compliance Ranges Comparison
ICM Japan
Mahindra and Mahindra Limited [Automotive and Farm Equipment Business]
Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for ICM Japan in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Mahindra and Mahindra Limited [Automotive and Farm Equipment Business] in 2026.
Incident History - ICM Japan (X = Date, Y = Severity)
ICM Japan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mahindra and Mahindra Limited [Automotive and Farm Equipment Business] (X = Date, Y = Severity)
Mahindra and Mahindra Limited [Automotive and Farm Equipment Business] cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ICM Japan
Mahindra and Mahindra Limited [Automotive and Farm Equipment Business]
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.