Comparison Overview
IOI Corporation Berhad
IOI Corporation Berhad
Lebuh IRC, IOI Resort City, Putrajaya, 62502, MY
Last Update: 28/03/2026
𝙸𝙾𝙸 Corporation Berhad is one of the leading global integrated and sustainable palm oil players. We are listed on the Main Market of Bursa Malaysia Securities Berhad and trading as MYX: 1961. Our plantation business covers Malaysia and Indonesia, and we currently h...
Syngenta
Rosentalstrasse 67, Basel, Basel, CH, 4002
Last Update: 02/04/2026
Syngenta is one of the world’s leading agriculture companies. Our ambition is to help safely feed the world while taking care of the planet. We aim to improve the sustainability, quality and safety of agriculture with world class science and innovative crop solutions. ...
Compliance Ranges Comparison
IOI Corporation Berhad
Syngenta
Benchmark & Cyber Underwriting Signals
Incidents vs Farming Industry Avg (This Year)
No incidents recorded for IOI Corporation Berhad in 2026.
Incidents vs Farming Industry Avg (This Year)
No incidents recorded for Syngenta in 2026.
Incident History - IOI Corporation Berhad (X = Date, Y = Severity)
IOI Corporation Berhad cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Syngenta (X = Date, Y = Severity)
Syngenta cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
IOI Corporation Berhad
Syngenta
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: *.*.