Comparison Overview
Perelman School of Medicine Center for Global Oncology
Perelman School of Medicine Center for Global Oncology
3600 Walnut Street, None, Philadelphia, PA, US, 19104
Last Update: 27/11/2025
The Penn Center for Global Oncology (CGO) is a bold new initiative at the intersection of cancer care and global health, launched to address the rising global cancer burden—particularly in low- and middle-income countries. As Penn Medicine’s coordinated response to this...
Texas Health Resources
612 E Lamar Blvd, Arlington, US
Last Update: 04/04/2026
At Texas Health Resources, our mission is to improve the health of the people in the communities we serve. We are one of the largest faith-based, nonprofit health systems in the United States with a team of more than 28,000 employees of wholly owned/operated facilities...
Compliance Ranges Comparison
Perelman School of Medicine Center for Global Oncology
Texas Health Resources
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Perelman School of Medicine Center for Global Oncology in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Texas Health Resources has 8.26% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Perelman School of Medicine Center for Global Oncology (X = Date, Y = Severity)
Perelman School of Medicine Center for Global Oncology cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Texas Health Resources (X = Date, Y = Severity)
Texas Health Resources cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Perelman School of Medicine Center for Global Oncology
Texas Health Resources
FAQ
Latest Global CVEs
A vulnerability was identified in ealpha072 Student-Management-System up to 01451bd7a2f58cdda07bd0b86e3967582e3ecd08. Affected by this issue is some unknown functionality of the file admin/config.php of the component Administrative Backend. Such manipulation leads to improper authentication. The attack may be performed from remote. The exploit is publicly available and might be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The project was informed of the problem early through an issue report but has not responded yet.
A vulnerability was determined in sgl-project SGLang up to 0.5.11. Affected by this vulnerability is the function data_hash of the component Cache Handler. This manipulation causes denial of service. The attack is restricted to local execution. A high degree of complexity is needed for the attack. The exploitation appears to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
Active IQ OneCollect version 2.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.
Active IQ Config Advisor version 6.7.3 contains hard-coded credentials that could allow an authenticated attacker with low privileges to perform unauthorized AutoSupport operations.
A vulnerability was found in crmeb crmeb_java 1.4. Affected is the function RestTemplate.getForEntity of the file crmeb-common/src/main/java/com/zbkj/common/utils/RestTemplateUtil.java of the component base64 Qrcode Endpoint. The manipulation of the argument url results in server-side request forgery. The attack can be executed remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.