Comparison Overview
Navitas Skilled Futures
Navitas Skilled Futures
255 Elizabeth St, Sydney, New South Wales, 2000, AU
Last Update: 28/03/2026
Navitas Skilled Futures (previously Navitas English) has been contracted by the Australian Government since 1990 to deliver programs that help people from diverse backgrounds improve their language, literacy, numeracy and digital skills (LLND) for a better future. Usi...
Bright Horizons
2 Wells Avenue, Newton, 02459, US
Last Update: 30/03/2026
More than 1,000 top employers trust Bright Horizons® (NYSE: BFAM) for proven solutions that support employees, advance careers, and maximize performance. From on-site child care that amplify your culture, back-up care to handle disruptions, and education programs that b...
Compliance Ranges Comparison
Navitas Skilled Futures
Bright Horizons
Benchmark & Cyber Underwriting Signals
Incidents vs Education Administration Programs Industry Avg (This Year)
No incidents recorded for Navitas Skilled Futures in 2026.
Incidents vs Education Administration Programs Industry Avg (This Year)
No incidents recorded for Bright Horizons in 2026.
Incident History - Navitas Skilled Futures (X = Date, Y = Severity)
Navitas Skilled Futures cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bright Horizons (X = Date, Y = Severity)
Bright Horizons cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Navitas Skilled Futures
Bright Horizons
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: *.*.