Comparison Overview
Woodland Heights Medical Center

Woodland Heights Medical Center
505 S. John Redditt Dr., Lufkin, 75904, US
Last Update: 31/05/2026
Woodland Heights Medical Center is your community healthcare provider, a 149-bed facility in Lufkin, TX, offering inpatient and outpatient services. We believe in the power of people to create great care. We're more than 200 healthcare professionals strong. We are a Joi...

UHS
367 S Gulph Rd, King of Prussia, 19406, US
Last Update: 16/09/2026
One of the nation’s largest and most respected providers of hospital and healthcare services, Universal Health Services, Inc. (NYSE: UHS) has built an impressive record of achievement and performance, growing since its inception into a Fortune 300 corporation. Headquart...
Compliance Ranges Comparison

Woodland Heights Medical Center







UHS






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Woodland Heights Medical Center in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for UHS in 2026.
Incident History - Woodland Heights Medical Center (X = Date, Y = Severity)
Woodland Heights Medical Center cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UHS (X = Date, Y = Severity)
UHS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Woodland Heights Medical Center

UHS
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout