Comparison Overview
DHL Group Investor Relations

DHL Group Investor Relations
Charles-de-Gaulle-Str. 20, Bonn, 53113, DE
Last Update: 23/12/2025
We are DHL Group’s Investor Relations specialists. We have a broad and exciting area of responsibility that takes in the entire spectrum of IR communications required by DHL Group, both as a listed company and as a leader in sustainable logistics. Investor Relations fun...

UPS Supply Chain Solutions
12380 Morris Rd, Alpharetta, GA, US, 30005
Last Update: 02/04/2026
UPS Supply Chain Solutions offers a comprehensive portfolio of services to enhance customers' business performance, including logistics and distribution, transportation and freight, consulting, customs brokerage, and international trade services. UPS provides the exper...
Compliance Ranges Comparison

DHL Group Investor Relations







UPS Supply Chain Solutions






Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for DHL Group Investor Relations in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for UPS Supply Chain Solutions in 2026.
Incident History - DHL Group Investor Relations (X = Date, Y = Severity)
DHL Group Investor Relations cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UPS Supply Chain Solutions (X = Date, Y = Severity)
UPS Supply Chain Solutions cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

DHL Group Investor Relations

UPS Supply Chain Solutions
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.