Comparison Overview
NEXECUR
NEXECUR
13, rue de Belle Ile, Coulaines, 72190, FR
Last Update: 14/03/2026
Spécialiste de la télésurveillance, des systèmes d’alarmes et de la téléassistance depuis près de 40 ans, Nexecur s'engage pour votre sécurité en s'appuyant sur l'expérience et la connaissance de vos besoins. Filiale sécurité du Crédit Agricole, Nexecur développe des s...
Australia Post
111 Bourke St, Melbourne, 3000, AU
Last Update: 14/09/2026
Connecting businesses with consumers is the heart of commercial prosperity and the cornerstone of Australia Post's commitment to Australian businesses. As connectivity transforms our lives, Australia Post is evolving to meet the future needs of businesses by providing t...
Compliance Ranges Comparison
NEXECUR
Australia Post
Benchmark & Cyber Underwriting Signals
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for NEXECUR in 2026.
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for Australia Post in 2026.
Incident History - NEXECUR (X = Date, Y = Severity)
NEXECUR cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Australia Post (X = Date, Y = Severity)
Australia Post cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
NEXECUR
Australia Post
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.