Comparison Overview
DMT ENCOS
DMT ENCOS
Blohmstraße 10, Hamburg, HH, 21079, DE
Last Update: 25/12/2025
Wir sind ein Engineering, Procurement, Construction Management (EPCM) Unternehmen und mit über 25 Jahren Anlagenplanungserfahrung führen wir erfolgreich Planungs- und Berechnungsleistungen von der Prozesssimulation bis zur Bauleitung in der Energieerzeugung, Apparate- u...
SABIC
PO Box 5101, Riyadh, SA, 11422
Last Update: 05/07/2026
SABIC is a global leader in chemicals headquartered in Riyadh, Saudi Arabia. From making cars and planes more fuel-efficient, to helping conserve the world’s water supply and enabling colorful smartphone cases, we find solutions to the challenges of today to help our cu...
Compliance Ranges Comparison
DMT ENCOS
SABIC
Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for DMT ENCOS in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for SABIC in 2026.
Incident History - DMT ENCOS (X = Date, Y = Severity)
DMT ENCOS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SABIC (X = Date, Y = Severity)
SABIC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
DMT ENCOS
SABIC
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: *.*.