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...
Aviva
80 Fenchurch Street, London, EC3M 4AE, , GB
Last Update: 04/09/2026
💛 We're a leading Insurance, Wealth & Retirement business. 📣 Follow for #LifeAtAviva. Aviva is nothing without our people. Living up to our purpose to be with you today for a better tomorrow applies to those we work with just as much as it does to our custom...
Compliance Ranges Comparison
Avemco Insurance Company
Aviva
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 Aviva 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 - Aviva (X = Date, Y = Severity)
Aviva cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Avemco Insurance Company
Aviva
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.