Comparison Overview
Aya Healthcare
Aya Healthcare
5930 Cornerstone Ct #300, San Diego, 92121, US
Last Update: 30/03/2026
Aya Healthcare is the largest healthcare talent software and staffing company in the United States. Aya operates the world’s largest digital staffing platform delivering every component of healthcare-focused labor services, including travel nursing and allied health, pe...
Manpower
100 Manpower Place, Milwaukee, WI, US, 53212
Last Update: 02/04/2026
Manpower is the global leader in contingent and permanent recruitment workforce solutions. We provide the agility businesses need with a continuum of staffing solutions. By leveraging our trusted brands, we have built a deeper talent pool to provide our clients access t...
Compliance Ranges Comparison
Aya Healthcare
Manpower
Benchmark & Cyber Underwriting Signals
Incidents vs Staffing and Recruiting Industry Avg (This Year)
No incidents recorded for Aya Healthcare in 2026.
Incidents vs Staffing and Recruiting Industry Avg (This Year)
No incidents recorded for Manpower in 2026.
Incident History - Aya Healthcare (X = Date, Y = Severity)
Aya Healthcare cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Manpower (X = Date, Y = Severity)
Manpower cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Aya Healthcare
Manpower
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: *.*.