Comparison Overview
INDISOL Bilişim ve Teknoloji

INDISOL Bilişim ve Teknoloji
Maslak Mah. Taşyoncası Sk. YTÜ Maslak 1453 Yerleşkesi No: 1 G İç Kapı No: B1 Kat: 10 , Sarıyer / İSTANBUL, İstanbul, Sarıyer, TR, 34398
Last Update: 01/02/2026
Indisol, teknoloji ve dijital dönüşümü odağına alıp yeni ve daha büyük başarılara imza atmak üzere OYAK bünyesinde öncelikle OYAK Grup Şirketlerine hizmet etmek amacıyla 2023 yılında kuruldu. Indisol, yazılım geliştirme ve yazılım teknoloji dönüşüm hizmeti sunan bir te...

Peraton
1875 Explorer St, Reston, 20190, US
Last Update: 14/09/2026
At Peraton, we're at the forefront of delivering the next big thing every day. We're the partner of choice to help solve some of the world's most daunting challenges, delivering bold, new solutions to keep people around the world safer and more secure. How do we do it?...
Compliance Ranges Comparison

INDISOL Bilişim ve Teknoloji







Peraton






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for INDISOL Bilişim ve Teknoloji in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Peraton in 2026.
Incident History - INDISOL Bilişim ve Teknoloji (X = Date, Y = Severity)
INDISOL Bilişim ve Teknoloji cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Peraton (X = Date, Y = Severity)
Peraton cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

INDISOL Bilişim ve Teknoloji

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