Comparison Overview
OYAK Mining Metallurgy
OYAK Mining Metallurgy
Barbaros Mah. Ardıç Sok. No:6 34746 Ataşehir İstanbul, İstanbul, 34746, TR
Last Update: 01/03/2026
OYAK Maden Metalürji olarak çalışanlarımız, müşterilerimiz, tedarikçilerimiz ve hissedarlarımızla birlikte Türkiye’nin küresel demir çelik gücüyüz. Yaklaşık 12.000 çalışanımızla Türkiye’nin en çok istihdam yaratan kuruluşlarından biriyiz. Uluslararası kalite standartl...
Vale
Praia de Botafogo, 186, Salas 501 a 1901 , Rio de Janeiro, Rio de Janeiro, BR, 22250-145
Last Update: 06/07/2026
We are a global mining company producing iron ore, pellets, and nickel, and we are committed to becoming one of the safest, most trustworthy mining company in the world. With a workforce of 120,000 employees, we work every day to transform natural resources into prosper...
Compliance Ranges Comparison
OYAK Mining Metallurgy
Vale
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for OYAK Mining Metallurgy in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Vale in 2026.
Incident History - OYAK Mining Metallurgy (X = Date, Y = Severity)
OYAK Mining Metallurgy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vale (X = Date, Y = Severity)
Vale cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
OYAK Mining Metallurgy
Vale
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: *.*.