Comparison Overview
Chapman Freeborn Flight Support

Chapman Freeborn Flight Support
3 City Place, , Gatwick, RH6 0PA, GB
Last Update: 21/03/2026
However complex or challenging the brief, our operations team delivers round-the-clock flight support on a global basis for both passenger and cargo operators. From ground handling and fuelling to aircraft catering and ground transfers, all can be arranged through our t...

Singapore Airlines
25 Airline Rd, Singapore, SG
Last Update: 03/07/2026
Welcome aboard Singapore Airlines on LinkedIn. Discover travel inspirations, business travel tips, cultural insights, our latest updates, and more. Singapore Airlines is a global company dedicated to providing air transportation services of the highest quality and to ...
Compliance Ranges Comparison

Chapman Freeborn Flight Support







Singapore Airlines






Benchmark & Cyber Underwriting Signals
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Chapman Freeborn Flight Support in 2026.
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Singapore Airlines in 2026.
Incident History - Chapman Freeborn Flight Support (X = Date, Y = Severity)
Chapman Freeborn Flight Support cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Singapore Airlines (X = Date, Y = Severity)
Singapore Airlines cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Chapman Freeborn Flight Support

Singapore Airlines
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: *.*.