Comparison Overview
Workana
Workana
Castillo 1366, Buenos Aires, City of Buenos Aires, 1414, AR
Last Update: 29/03/2026
With +10 years in the market, Workana is the largest remote work platform for hiring top talent in Latin America. We match great talent with exciting opportunities and we love doing it. We believe remote work promotes equal and unprecedented growth opportunities for b...
Remote
San Francisco, 94133, US
Last Update: 02/04/2026
Talent is everywhere. Opportunity is not. Remote's mission is to create opportunity everywhere, empowering employers to find and hire the best talent, and enabling individuals to build financial and personal freedom. Remote is the all-in-one HR and payroll platform to...
Compliance Ranges Comparison
Workana
Remote
Benchmark & Cyber Underwriting Signals
Incidents vs Human Resources Services Industry Avg (This Year)
No incidents recorded for Workana in 2026.
Incidents vs Human Resources Services Industry Avg (This Year)
No incidents recorded for Remote in 2026.
Incident History - Workana (X = Date, Y = Severity)
Workana cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Remote (X = Date, Y = Severity)
Remote cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Workana
Remote
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: *.*.