Comparison Overview
Access Healthcare
Access Healthcare
4300 Alpha Rd, Dallas, 75244, US
Last Update: 03/09/2026
Established in 2011, Access Healthcare remains at the forefront of healthcare management, allowing providers to focus on what matters most – their patients. Our reputation is built on investing in and developing innovative technology allowing us to deliver custom soluti...
The University of Texas Medical Branch
301 University Blvd, Galveston, Texas, US, 77550
Last Update: 06/09/2026
The first academic health center in Texas opened its doors in 1891 and today has four campuses, five health sciences schools, seven institutes for advanced study, a research enterprise that includes one of only two national laboratories dedicated to the safe study of in...
Compliance Ranges Comparison
Access Healthcare
The University of Texas Medical Branch
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Access Healthcare in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for The University of Texas Medical Branch in 2026.
Incident History - Access Healthcare (X = Date, Y = Severity)
Access Healthcare cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The University of Texas Medical Branch (X = Date, Y = Severity)
The University of Texas Medical Branch cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Access Healthcare
The University of Texas Medical Branch
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.