Comparison Overview
Moralis
Moralis
Stockholm, SE
Last Update: 12/06/2026
Moralis | Fetch, Monitor & Export Crypto Data Moralis is the complete crypto data layer. Fetch blockchain data with our Data APIs, monitor crypto data with Streams, and export massive blockchain datasets with Datashare. Made by developers for developers. Trusted by 15...
Cox Automotive Inc.
3003 Summit Blvd., 200, Atlanta, GA, US, 30319
Last Update: 12/09/2026
Cox Automotive is the world’s largest automotive services and technology provider. Fueled by the largest breadth of first- and third-party data fed by 2.3 billion online interactions a year, Cox Automotive tailors leading solutions for car shoppers, auto manufacturers, ...
Compliance Ranges Comparison
Moralis
Cox Automotive Inc.
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
Moralis has 6.54% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Cox Automotive Inc. in 2026.
Incident History - Moralis (X = Date, Y = Severity)
Moralis cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Cox Automotive Inc. (X = Date, Y = Severity)
Cox Automotive Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Moralis
Cox Automotive Inc.
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.