Comparison Overview
ARCHER
ARCHER
New York, US
Last Update: 20/03/2026
ARCHER, the social-first dating app for gay, bisexual, and queer men, creates a celebratory place, designed with safety in mind, where users can express themselves and build connections freely. On ARCHER, everyone shows a face. For more information, visit www.archerapp...
Arrow Electronics
9201 East Dry Creek Road, Centennial, 80112, US
Last Update: 13/09/2026
Arrow Electronics (NYSE:ARW) guides innovation forward for thousands of leading technology manufacturers and service providers. With 2024 sales of $27.9 billion, Arrow develops technology solutions that help improve business and daily life. Our broad portfolio that spa...
Compliance Ranges Comparison
ARCHER
Arrow Electronics
Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for ARCHER in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Arrow Electronics in 2026.
Incident History - ARCHER (X = Date, Y = Severity)
ARCHER cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Arrow Electronics (X = Date, Y = Severity)
Arrow Electronics cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
ARCHER
Arrow Electronics
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.