Comparison Overview
TAP Air Portugal
TAP Air Portugal
Aeroporto de Lisboa, Lisbon, undefined, 1704-801, PT
Last Update: 01/04/2026
TAP is Portugal’s leading airline and is a member of Star Alliance since 2005. Flying since 1945, TAP Air Portugal has its hub in Lisbon, a privileged access platform in Europe, at the crossroads with Africa, North, Central, and South America. The Portuguese airline is ...
Cathay Pacific
Cathay City, 8 Scenic Road, Chek Lap Kok, HK
Last Update: 27/06/2026
Welcome to the official Cathay Pacific LinkedIn page. We have over 200 destinations in our global network, but want to do more than just move you from A to B. We want to take you further in your journey, and ultimately, to move beyond. And we’re here to do what we can t...
Compliance Ranges Comparison
TAP Air Portugal
Cathay Pacific
Benchmark & Cyber Underwriting Signals
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for TAP Air Portugal in 2026.
Incidents vs Airlines and Aviation Industry Avg (This Year)
No incidents recorded for Cathay Pacific in 2026.
Incident History - TAP Air Portugal (X = Date, Y = Severity)
TAP Air Portugal cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cathay Pacific (X = Date, Y = Severity)
Cathay Pacific cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
TAP Air Portugal
Cathay Pacific
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: *.*.