Comparison Overview
Hartz Mountain Corporation
Hartz Mountain Corporation
1, Secaucus, NJ, undefined, US
Last Update: 02/04/2026
🐾 For more than 95 years, Hartz has been solely focused on providing pet care products that give pets the Unconditional Love that they give us. Our Mission is to strengthen the bond between pets and their families by providing innovative, trustworthy, and affordable ...
Vedanta Group
Vedanta Resources, London, GB
Last Update: 20/04/2026
We operate on the belief that our people are our core assets and we consistently endeavour towards developing their potential to be our future leaders and key employees. We currently operate in India, South Africa, Liberia and Namibia, through our various subsidiaries. ...
Compliance Ranges Comparison
Hartz Mountain Corporation
Vedanta Group
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Hartz Mountain Corporation in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
Vedanta Group has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Hartz Mountain Corporation (X = Date, Y = Severity)
Hartz Mountain Corporation cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vedanta Group (X = Date, Y = Severity)
Vedanta Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hartz Mountain Corporation
Vedanta Group
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: *.*.