Comparison Overview
Pardakht Novin
Pardakht Novin
No.21 , South Allame, Saadat Abad , Tehran, undefined, 1997979984, IR
Last Update: 25/10/2025
Pardakht Novin was founded in March 2006 aiming at expanding the network of innovative electronic payment services. The company is currently active in the field of electronic payment as one of the companies licensed by the Central Bank and Shaparak Payment System. Endow...
Halkbank
Şebboy Sokak, Ataşehir, 34746, TR
Last Update: 02/04/2026
23 Mayıs 1938 tarihinde faaliyete geçen Halkbank, kuruluşundan bu yana reel sektöre kesintisiz finansal destek misyonuyla çalışarak, bireysel ve kurumsal müşterilerine bankacılık ürün ve hizmetlerini üstün bir kalitede sunmaktadır. Halkbank, halktan ve çalışanlarından ...
Compliance Ranges Comparison
Pardakht Novin
Halkbank
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Pardakht Novin in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Halkbank in 2026.
Incident History - Pardakht Novin (X = Date, Y = Severity)
Pardakht Novin cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Halkbank (X = Date, Y = Severity)
Halkbank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pardakht Novin
Halkbank
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.