Comparison Overview
VIDARA Turkey Kimya Tic. A.Ş.

VIDARA Turkey Kimya Tic. A.Ş.
Begonya Sokak, Ataşehir, 34746, TR
Last Update: 01/04/2026
Vidara Turkey Kimya as KEMIROPA has started the business in 1987 by offering specialty chemicals to the coating and inks industries imported from the worldwide technologically leading companies. In addition, Ravago Chemicals Turkey is now serving through her specialised...

Linde
43 Church Street West, Woking, GU21 6HT, GB
Last Update: 01/07/2026
Linde is a leading global industrial gases and engineering company with 2025 sales of $34 billion. We live our mission of making our world more productive every day by providing high-quality solutions, technologies and services which are making our customers more succes...
Compliance Ranges Comparison

VIDARA Turkey Kimya Tic. A.Ş.







Linde






Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
VIDARA Turkey Kimya Tic. A.Ş. has 60.78% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Linde in 2026.
Incident History - VIDARA Turkey Kimya Tic. A.Ş. (X = Date, Y = Severity)
VIDARA Turkey Kimya Tic. A.Ş. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Linde (X = Date, Y = Severity)
Linde cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

VIDARA Turkey Kimya Tic. A.Ş.

Linde
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: *.*.