Comparison Overview
Honor
Honor
201 3rd St, San Francisco, California, 94103, US
Last Update: 27/02/2026
For the first time in history, older adults outnumber the young, making caring for the aging population one of society’s biggest challenges. Honor sees this challenge as an opportunity to combine the compassion of care professionals with the latest technology to bridge ...
Tenet Healthcare
14201 Dallas Pkwy, Dallas, 75254, US
Last Update: 26/06/2026
Tenet Healthcare Corporation (NYSE: THC) is a diversified healthcare services company headquartered in Dallas. Our care delivery network includes United Surgical Partners International, the largest ambulatory platform in the country, which operates ambulatory surgery ce...
Compliance Ranges Comparison
Honor
Tenet Healthcare
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Honor in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Tenet Healthcare in 2026.
Incident History - Honor (X = Date, Y = Severity)
Honor cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tenet Healthcare (X = Date, Y = Severity)
Tenet Healthcare cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Honor
Tenet Healthcare
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: *.*.