Comparison Overview
Fetcher
Fetcher
335 Madison Ave, New York, New York, 10017, US
Last Update: 09/12/2025
Fetcher connects you with top talent globally to help turn business dreams into reality. Whether you want to hire fast, enhance diversity, broaden your pool of skilled individuals, or just save time finding candidates, we're eager to please. Talent Sourcing: With Fetc...
IDEMIA
2 place Samuel Champlain, Courbevoie, 92400, FR
Last Update: 11/09/2026
IDEMIA Secure Transactions (IST) is a leading provider of payment, connectivity, and cybersecurity solutions, serving billions of people worldwide. With decades of expertise in cryptography and credential issuance, IST is trusted by over 2000 financial institutions, mob...
Compliance Ranges Comparison
Fetcher
IDEMIA
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Fetcher in 2026.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for IDEMIA in 2026.
Incident History - Fetcher (X = Date, Y = Severity)
Fetcher cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IDEMIA (X = Date, Y = Severity)
IDEMIA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Fetcher
IDEMIA
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.