Comparison Overview
Krones.digital
Krones.digital
N/A
Last Update: 18/04/2026
Krones.digital is the community for all digital topics in the Krones Group with over 500 experts all over the world. We bundle all forces and competences in the areas of digitalization and automation. We form a matrix organization in which colleagues think and work toge...
Carelon Global Solutions India
Indianapolis, Indianapolis, 46204, US
Last Update: 11/09/2026
Carelon Global Solutions makes healthcare operations more practical, effective, and efficient. Our global team of more than 25K innovators drives growth, delivers exceptional support, and develops digital tools specifically for health plans, providers, and systems. Each...
Compliance Ranges Comparison
Krones.digital
Carelon Global Solutions India
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Krones.digital in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Carelon Global Solutions India in 2026.
Incident History - Krones.digital (X = Date, Y = Severity)
Krones.digital cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Carelon Global Solutions India (X = Date, Y = Severity)
Carelon Global Solutions India cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Krones.digital
Carelon Global Solutions India
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.