Comparison Overview
Dan L Duncan Comprehensive Cancer Center

Dan L Duncan Comprehensive Cancer Center
1919 Old Spanish Trail, Houston, 77054, US
Last Update: 11/03/2026
The Dan L Duncan Comprehensive Cancer Center at Baylor College of Medicine brings together cancer-related activities under one umbrella, fast-tracking our efforts to prevent, diagnose and more effectively treat cancer.

Kaiser Permanente
1 Kaiser Plaza, Oakland, 94612, US
Last Update: 04/04/2026
At the heart of health care, you’ll find Kaiser Permanente. As the nation’s leading not-for-profit, integrated health plan, we make a difference in the lives of members, patients, and communities across the country. With 39 hospitals and more than 734 locations in eig...
Compliance Ranges Comparison

Dan L Duncan Comprehensive Cancer Center







Kaiser Permanente






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Dan L Duncan Comprehensive Cancer Center in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
Kaiser Permanente has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Dan L Duncan Comprehensive Cancer Center (X = Date, Y = Severity)
Dan L Duncan Comprehensive Cancer Center cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Kaiser Permanente (X = Date, Y = Severity)
Kaiser Permanente cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Dan L Duncan Comprehensive Cancer Center

Kaiser Permanente
FAQ
Latest Global CVEs
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.
An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.