Comparison Overview
Glencore South Africa
Glencore South Africa
39 Melrose Blvd, Birnam, Sandton, 2076, Johannesburg, Gauteng, 2191, ZA
Last Update: 05/12/2025
Glencore plc is one of the world’s largest global diversified natural resource companies and a major producer and trader of more than 90 commodities.
Maaden
Saudi Arabia, Riyadh, SA, 11537
Last Update: 10/06/2026
Maaden is Saudi Arabia’s engine of industrial transformation and one of the world’s top ten mining giants by market cap and fastest growing globally. We’re building the future of mining, creating fully integrated value chains across gold, phosphate, bauxite, copper and ...
Compliance Ranges Comparison
Glencore South Africa
Maaden
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Glencore South Africa in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Maaden in 2026.
Incident History - Glencore South Africa (X = Date, Y = Severity)
Glencore South Africa cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Maaden (X = Date, Y = Severity)
Maaden cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Glencore South Africa
Maaden
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: *.*.