Comparison Overview
Private Sector Roundtable on Global Health Security (PSRT)

Private Sector Roundtable on Global Health Security (PSRT)
N/A
Last Update: 09/12/2025
We are a leading voice on private sector engagement in global health security, with member companies from diverse industries. We are committed to leveraging private sector expertise and resources to help achieve the vision of a world safe from global health threats -- a...

U.S. Department of State
2201 C St., NW, Washington, 20520, US
Last Update: 30/03/2026
The U.S. Department of State is focused on accomplishing America's mission of diplomacy at home and around the world. The U.S. Department of State manages America’s relationships with foreign governments, international organizations, and the people of other countries. U...
Compliance Ranges Comparison

Private Sector Roundtable on Global Health Security (PSRT)







U.S. Department of State






Benchmark & Cyber Underwriting Signals
Incidents vs International Affairs Industry Avg (This Year)
No incidents recorded for Private Sector Roundtable on Global Health Security (PSRT) in 2026.
Incidents vs International Affairs Industry Avg (This Year)
No incidents recorded for U.S. Department of State in 2026.
Incident History - Private Sector Roundtable on Global Health Security (PSRT) (X = Date, Y = Severity)
Private Sector Roundtable on Global Health Security (PSRT) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - U.S. Department of State (X = Date, Y = Severity)
U.S. Department of State cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Private Sector Roundtable on Global Health Security (PSRT)

U.S. Department of State
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.