Comparison Overview
Avemco Insurance Company
Avemco Insurance Company
8490 Progress Dr, Suite 200, Frederick, Maryland, US, 21701
Last Update: 23/03/2026
Avemco Insurance Company, a leading pleasure and business general aviation insurer in the United States, has been insuring planes and pilots since 1961. Headquartered in Frederick, Maryland, Avemco is rated A++ (Superior) by A. M. Best. Avemco is a subsidiary of Tokio M...
Humana
500 W Main St, Louisville, US
Last Update: 01/04/2026
Humana will never ask, nor require a candidate to provide money for work equipment and network access during the application process. If you become aware of any instances where you as a candidate are asked to provide information and do not believe it is a legitimate req...
Compliance Ranges Comparison
Avemco Insurance Company
Humana
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Avemco Insurance Company in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Humana in 2026.
Incident History - Avemco Insurance Company (X = Date, Y = Severity)
Avemco Insurance Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Humana (X = Date, Y = Severity)
Humana cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Avemco Insurance Company
Humana
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: *.*.