Comparison Overview
Smart Omix by Sharecare
Smart Omix by Sharecare
undefined, Atlanta, undefined, undefined, US
Last Update: 10/11/2025
Smart Omix by Sharecare is a software platform enabling researchers to design, launch, manage, and analyze real-world digital clinical studies at scale. Researchers across the healthcare and life sciences industry can leverage our self-service platform or concierge stu...
Everforth
N/A
Last Update: 12/09/2026
Everforth, Inc. (NYSE: EFOR) is a leading technology and digital engineering company that helps organizations adapt, innovate, and thrive in a world of constant change. Our six solution areas — AI and data, cloud and infrastructure, application and digital engineering, ...
Compliance Ranges Comparison
Smart Omix by Sharecare
Everforth
Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Smart Omix by Sharecare in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Everforth in 2026.
Incident History - Smart Omix by Sharecare (X = Date, Y = Severity)
Smart Omix by Sharecare cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Everforth (X = Date, Y = Severity)
Everforth cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Smart Omix by Sharecare
Everforth
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.