Comparison Overview
Safran – Aircraft Interiors

Safran – Aircraft Interiors
N/A
Last Update: 19/02/2026
Safran Cabin's mission is to design, certify, manufacture, and support the world's most innovative aircraft cabin interiors, providing airlines and OEM customers with distinctive aircraft branding, and their passengers with the safe, comfortable and enjoyable flying exp...

Boeing
929 Long Bridge Drive, Arlington, 22202, US
Last Update: 03/06/2026
Boeing is a leading global aerospace company that designs, builds and supports commercial airplanes, defense products and space systems for customers in more than 150 countries. Guided by our commitment to safety and quality, we innovate to deliver solutions that bring ...
Compliance Ranges Comparison

Safran – Aircraft Interiors







Boeing






Benchmark & Cyber Underwriting Signals
Incidents vs Aviation & Aerospace Industry Avg (This Year)
No incidents recorded for Safran – Aircraft Interiors in 2026.
Incidents vs Aviation & Aerospace Industry Avg (This Year)
No incidents recorded for Boeing in 2026.
Incident History - Safran – Aircraft Interiors (X = Date, Y = Severity)
Safran – Aircraft Interiors cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Boeing (X = Date, Y = Severity)
Boeing cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Safran – Aircraft Interiors

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