Comparison Overview
Koç Bilgi ve Savunma Teknolojileri
Koç Bilgi ve Savunma Teknolojileri
ODTÜ Teknokent Yazılım Teknoparkı Üniversiteler Mah. İhsan Doğramacı Bulvarı No:17/B , Ankara, Üniversiteler Mah., 06800, TR
Last Update: 12/12/2025
Koç Bilgi ve Savunma Teknolojileri, ulusal ve uluslararası boyutta örnek olacak projelerin hayata geçirilmesi konusunda çalışmakta ve bilimsel yaklaşımların ışığında çözümler üretmektedir. Ar-Ge odaklı temel çalışma başlıkları aşağıdaki gibidir: • Savunma Sanayii •...
BAE Systems
BAE Systems, London, SW1Y 5AD, GB
Last Update: 01/04/2026
At BAE Systems, we help our customers to stay a step ahead when protecting people and national security, critical infrastructure and vital information. We provide some of the world’s most advanced, technology-led defence, aerospace and security solutions and employ a sk...
Compliance Ranges Comparison
Koç Bilgi ve Savunma Teknolojileri
BAE Systems
Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Koç Bilgi ve Savunma Teknolojileri in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for BAE Systems in 2026.
Incident History - Koç Bilgi ve Savunma Teknolojileri (X = Date, Y = Severity)
Koç Bilgi ve Savunma Teknolojileri cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BAE Systems (X = Date, Y = Severity)
BAE Systems cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Koç Bilgi ve Savunma Teknolojileri
BAE Systems
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: *.*.