Comparison Overview
C+Y Medical PC
C+Y Medical PC
N/A
Last Update: 30/07/2026
Welcome to our practice! We are glad you have chosen us for your health needs and hope that every encounter with our office and staff exceeds your expectations. We know our patients have a choice in several different areas, so we go out of our way to deliver the level o...
UnityPoint Health
1776 West Lakes Parkway,, West Des Moines, 50266, US
Last Update: 13/09/2026
As an integrated health system, we provide care throughout Iowa, western Illinois and southern Wisconsin in not-for-profit hospitals, clinics and home health settings. Each year, we serve nearly 8 million patient visits of all different types, including around 100,000 s...
Compliance Ranges Comparison
C+Y Medical PC
UnityPoint Health
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for C+Y Medical PC in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for UnityPoint Health in 2026.
Incident History - C+Y Medical PC (X = Date, Y = Severity)
C+Y Medical PC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UnityPoint Health (X = Date, Y = Severity)
UnityPoint Health cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
C+Y Medical PC
UnityPoint Health
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.