Comparison Overview
Saab, Inc.
Saab, Inc.
85 Collamer Crossings, None, East Syracuse, New York, US, 13057
Last Update: 21/03/2026
Saab serves the U.S. government, industry, and commercial customers with world-leading products, services and solutions ranging from military defense to civil security. We constantly develop, adopt and improve new technology to meet changing customer needs. With approxi...
Naval Sea Systems Command (NAVSEA) Careers
N/A
Last Update: 01/04/2026
We are NAVSEA. The Force Behind the Fleet. Join us and become part of a mission-driven team, at one of the best places to work in the federal government. This NAVSEA LinkedIn page is all about connecting with talented individuals ready to make a difference through a rew...
Compliance Ranges Comparison
Saab, Inc.
Naval Sea Systems Command (NAVSEA) Careers
Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Saab, Inc. in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Naval Sea Systems Command (NAVSEA) Careers in 2026.
Incident History - Saab, Inc. (X = Date, Y = Severity)
Saab, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Naval Sea Systems Command (NAVSEA) Careers (X = Date, Y = Severity)
Naval Sea Systems Command (NAVSEA) Careers cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Saab, Inc.
Naval Sea Systems Command (NAVSEA) Careers
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: *.*.