Comparison Overview
Sitecore Italia

Sitecore Italia
Via Giuseppe Mazzini, 9, Milan, 20123, IT
Last Update: 26/03/2026
Benvenuti nella Business Community di Sitecore Italia! Partecipa alla nostra community per conoscere l’innovazione delle nostre soluzioni componibili, partecipare alle nostre iniziative, lasciarti trasportare dalle storie di successo dei nostri clienti e partner, far p...

OpenText
275 Frank Tompa Drive, Waterloo, N2L 0A1, CA
Last Update: 11/09/2026
OpenText is a leading Cloud and AI company that provides organizations around the world with a comprehensive suite of Business AI, Business Clouds, and Business Technology. We help organizations grow, innovate, become more efficient and effective, and do so in a trusted...
Compliance Ranges Comparison

Sitecore Italia







OpenText






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Sitecore Italia in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for OpenText in 2026.
Incident History - Sitecore Italia (X = Date, Y = Severity)
Sitecore Italia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - OpenText (X = Date, Y = Severity)
OpenText cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sitecore Italia

OpenText
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.