Comparison Overview
Odgers USA
Odgers USA
730 3rd Ave, 23rd Floor, New York, NY, US, 10017
Last Update: 02/04/2026
Odgers transforms organizational performance by recruiting and developing exceptional leaders and teams. Our global network of over 1,200 colleagues in 33 countries, means we have local knowledge powered by international insights and connections to create meaningful imp...
KPMG India
Building No. 10, 8th Floor, Tower B,, Gurugram, 122002, IN
Last Update: 02/04/2026
KPMG entities in India are established under the laws of India and are owned and managed (as the case may be) by established Indian professionals. Established in September 1993, the KPMG entities have rapidly built a significant competitive presence in the country. Toda...
Compliance Ranges Comparison
Odgers USA
KPMG India
Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for Odgers USA in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for KPMG India in 2026.
Incident History - Odgers USA (X = Date, Y = Severity)
Odgers USA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - KPMG India (X = Date, Y = Severity)
KPMG India cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Odgers USA
KPMG India
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: *.*.