Comparison Overview
Singing River Health System
Singing River Health System
3109 Bienville Blvd, Ocean Springs, 39564, US
Last Update: 20/05/2026
Singing River offers award-winning, comprehensive care for every age and stage. As one of South Mississippi's largest employers and proudly recognized on the Forbes list of America’s Best-In-State Employers, we are committed to the highest quality standards and attracti...
Alberta Health Services
10030 – 107 Street NW, Edmonton, T5J 3E4, CA
Last Update: 06/05/2026
Alberta Health Services (AHS) is proud to be part of Canada’s first and largest provincewide, integrated health system, responsible for delivering health services to more than 4.5 million people living in Alberta, as well as occasionally to some residents of other provi...
Compliance Ranges Comparison
Singing River Health System
Alberta Health Services
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Singing River Health System in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Alberta Health Services has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Singing River Health System (X = Date, Y = Severity)
Singing River Health System cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Alberta Health Services (X = Date, Y = Severity)
Alberta Health Services cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Singing River Health System
Alberta Health Services
FAQ
Latest Global CVEs
Redis contains a use-after-free vulnerability in the 'tlsProcessPendingData()' function, which handles the TLS pending-data list if Redis is configured with TLS support. A remote, unauthenticated attacker may be able to execute arbitrary commands with the privileges of the Redis server. Fixed in Redis 8.2.9, 8.4.6, 8.6.6, 8.8.2, and 8.10.1.
- https://github.com/redis/redis/commit/6d088c335d5c3ec49a6c28486140b498e70b7834
- https://github.com/v12-security/pocs/tree/main/redis/server_ssl
- https://raw.githubusercontent.com/redis/redis/8.10/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.2/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.4/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.6/00-RELEASENOTES
- https://raw.githubusercontent.com/redis/redis/8.8/00-RELEASENOTES
Unrestricted Upload of File with Dangerous Type in the product photo upload in Roskus Prospero Flow CRM before 5.16.0 allows an authenticated user holding the create product permission (routine Seller role) to execute arbitrary JavaScript in the application origin. The photo validation rule classifies the file only by its content (magic bytes) and rejects only a fixed list of PHP extensions, while ProductSaveController::save() names the stored file using the client-supplied extension and copies it into the public web root. A file that begins with an image header and carries an HTML extension passes validation, is stored under public/asset/upload/product/, and is served with a text/html content type, turning the upload into first-party stored script execution.
A flaw was found in gdk-pixbuf. When loading a specially crafted JPEG image containing chunked ICC profile markers, an error during ICC profile parsing can leave stale size metadata after the profile buffer is freed. A subsequent allocation in the same decode can cause an out-of-bounds write, potentially crashing the application. To exploit this flaw, an application using gdk-pixbuf must process the malicious JPEG image. Affected version >= 2.26.4
A relative path traversal issue in the zip extraction functionality in AWS diagram-as-code (awsdac) in versions 0.10 through 0.23 can allow a third party to write arbitrary files to the local filesystem via crafted zip entry names containing path traversal sequences. This could allow the third party to perform inappropriate actions in the diagram bundle. To remediate this issue, users should upgrade to the version 0.24 or later.
A weakness has been identified in RooCodeInc Roo-Code up to 3.51.1. Affected by this issue is the function ExecaTerminalProcess of the component README File Handler. Executing a manipulation can lead to code injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. Multiple isses were reported to the vendor beforehand. They explain, that "they all apply to Roo Code, a project we no longer support - the repository was archived a while ago, and we don't encourage anyone to use it." This vulnerability only affects products that are no longer supported by the maintainer.