Comparison Overview
Microsoft Threat Intelligence
Microsoft Threat Intelligence
Redmond, US
Last Update: 12/09/2026
The Microsoft Threat Intelligence community is made up of more than 10,000 world-class experts, security researchers, analysts, and threat hunters analyzing 78 trillion signals daily to discover threats and deliver timely and hyper-relevant insight to protect customers....
CrowdStrike
Remote, US
Last Update: 13/09/2026
CrowdStrike (Nasdaq: CRWD), a global cybersecurity leader, has redefined modern security with the world’s most advanced cloud-native platform for protecting critical areas of enterprise risk — endpoints and cloud workloads, identity and data. Powered by the CrowdStrike...
Compliance Ranges Comparison
Microsoft Threat Intelligence
CrowdStrike
Benchmark & Cyber Underwriting Signals
Incidents vs Computer and Network Security Industry Avg (This Year)
Microsoft Threat Intelligence has 2056.86% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Computer and Network Security Industry Avg (This Year)
CrowdStrike has 676.7% more incidents than the average of all companies with at least one recorded incident.
Incident History - Microsoft Threat Intelligence (X = Date, Y = Severity)
Microsoft Threat Intelligence cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CrowdStrike (X = Date, Y = Severity)
CrowdStrike cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Microsoft Threat Intelligence
CrowdStrike
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.