Comparison Overview
H&R Block

H&R Block
One H&R Block Way, Kansas City, 64105, US
Last Update: 31/03/2026
H&R Block’s purpose is simple: To provide help and inspire confidence in our clients and communities everywhere. We’ve been true to that purpose since brothers Henry and Richard Bloch founded our company in 1955. Since then, we’ve prepared approximately 800 million tax ...

Conad
Bologna, 40100, IT
Last Update: 01/04/2026
PERSONE OLTRE LE COSE. Conad è una storia fatta di imprenditori, commercianti, clienti e comunità. Un lungo viaggio che inizia nella metà degli anni ’60: nel 1962 nasce a Bologna il Consorzio Nazionale Dettaglianti, una società cooperativa a responsabilità limitata cost...
Compliance Ranges Comparison

H&R Block







Conad






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for H&R Block in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Conad in 2026.
Incident History - H&R Block (X = Date, Y = Severity)
H&R Block cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Conad (X = Date, Y = Severity)
Conad cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

H&R Block

Conad
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: *.*.