Comparison Overview
Personal Touch Home Care
Personal Touch Home Care
1985 Marcus Avenue, Lake Success, 11042, US
Last Update: 01/04/2026
PERSONAL-TOUCH HOME CARE, began operations in 1974 and since then has grown into a national company. Each office is licensed by the State in which it operates and most of the offices are certified as home health agencies offering Medicare services. We provide skilled nu...
Geisinger
100 North Academy Avenue, Danville, Pa., US, 17822
Last Update: 11/09/2026
Geisinger is among the nation’s leading providers of value-based care, serving 1.2 million people in urban and rural communities across Pennsylvania. Founded in 1915 by philanthropist Abigail Geisinger, the nonprofit system generates $10 billion in annual revenues acros...
Compliance Ranges Comparison
Personal Touch Home Care
Geisinger
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Personal Touch Home Care in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Geisinger has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Personal Touch Home Care (X = Date, Y = Severity)
Personal Touch Home Care cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Geisinger (X = Date, Y = Severity)
Geisinger cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Personal Touch Home Care
Geisinger
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.