Comparison Overview
Compunnel India
Compunnel India
Noida, 201301, IN
Last Update: 24/02/2026
Compunnel Inc. is where AI-native solutions meet human ingenuity, helping enterprises reimagine talent, technology, and growth. A world where your people and your platforms don’t just coexist — they co-elevate. At Compunnel, we build bridges between intelligent systems...
IBM
International Business Machines Corp., Armonk, New York, 10504, US
Last Update: 15/09/2026
At IBM, we do more than work. We create. We create as technologists, developers, and engineers. We create with our partners. We create with our competitors. If you're searching for ways to make the world work better through technology and infrastructure, software and co...
Compliance Ranges Comparison
Compunnel India
IBM
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Compunnel India in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
IBM has 1065.05% more incidents than the average of all companies with at least one recorded incident.
Incident History - Compunnel India (X = Date, Y = Severity)
Compunnel India cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IBM (X = Date, Y = Severity)
IBM cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Compunnel India
IBM
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.