Comparison Overview
Managed Care Systems, Inc.
Managed Care Systems, Inc.
N/A
Last Update: 01/04/2026
MCSI is a leader in automation and innovative software solutions. We rely upon the breadth of our experience and our industry proven tools to deliver top-notch results. We love proto-type development but also take the measure-twice cut once approach of test-based develo...
ServiceNow
2225 Lawson Lane, Santa Clara, 95054, US
Last Update: 09/09/2026
ServiceNow (NYSE: NOW) makes the world work better for everyone. Our cloud-based platform and solutions help digitize and unify organizations so that they can find smarter, faster, better ways to make work flow. So employees and customers can be more connected, more inn...
Compliance Ranges Comparison
Managed Care Systems, Inc.
ServiceNow
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Managed Care Systems, Inc. in 2026.
Incidents vs Software Development Industry Avg (This Year)
ServiceNow has 579.61% more incidents than the average of all companies with at least one recorded incident.
Incident History - Managed Care Systems, Inc. (X = Date, Y = Severity)
Managed Care Systems, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ServiceNow (X = Date, Y = Severity)
ServiceNow cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Managed Care Systems, Inc.
ServiceNow
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.