Comparison Overview
Central Payment
Central Payment
2350 Kerner Blvd. Suite 300, San Rafael, 94901, US
Last Update: 29/03/2026
Central Payment is-a leading national Merchant Service Provider, offering businesses across the country a secure method of handling all electronic transactions including credit card processing, gift cards, wireless/mobile solutions, virtual terminals, point of sale syst...
Morningstar
22 W. Washington St., Chicago, IL, US, 60602
Last Update: 13/09/2026
Morningstar, Inc. is a leading provider of independent investment insights in North America, Europe, Australia, and Asia. The Company offers an extensive line of products and services for individual investors, financial advisors, asset managers and owners, retirement pl...
Compliance Ranges Comparison
Central Payment
Morningstar
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Central Payment in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Morningstar in 2026.
Incident History - Central Payment (X = Date, Y = Severity)
Central Payment cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Morningstar (X = Date, Y = Severity)
Morningstar cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Central Payment
Morningstar
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.