Comparison Overview
Feijen | Tata Steel Nederland
Feijen | Tata Steel Nederland
Fregatweg 42, Maastricht, 6222 NZ, NL
Last Update: 22/01/2026
Our service centre in Maastricht (Feijen) is part of our highly specialised distribution service for the European heavy gauge market.
Orica
1 Nicholson St, East Melbourne, 3000, AU
Last Update: 01/04/2026
Our story began in 1874, when we first supplied explosives to the Victorian goldfields in Australia. Since then, we have grown to become one of the world’s leading mining and infrastructure solutions providers. From the production and supply of explosives, blasting s...
Compliance Ranges Comparison
Feijen | Tata Steel Nederland
Orica
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Feijen | Tata Steel Nederland in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Orica in 2026.
Incident History - Feijen | Tata Steel Nederland (X = Date, Y = Severity)
Feijen | Tata Steel Nederland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Orica (X = Date, Y = Severity)
Orica cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Feijen | Tata Steel Nederland
Orica
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: *.*.