Comparison Overview
DHL Express Japan

DHL Express Japan
東品川1-37-8, 品川区, 東京都 1400002, JP
Last Update: 20/04/2026
DHL Expressは、世界220以上の国と地域をスピーディーに結ぶエアネットワークを築き、国際エクスプレスのリーディングカンパニーとして、オンラインショッピングから企業の国際貿易まで、人々の生活やビジネスを国際輸送でサポートしています。 DHLジャパン株式会社について DHLジャパンは、DHLグループの日本支社として1972年にサービスを開始しました。 DHLジャパンは、Great Place To Work® Institute Japanが発表する、日本における「働きがいのある会社」ランキングにおいて、13年連続でベストカン...

Expeditors
3545 Factoria Blvd SE, Bellevue, 98006, US
Last Update: 13/09/2026
Expeditors is a Fortune 500 service-based logistics company with headquarters in Seattle, Washington, USA. At Expeditors, we generate highly optimized and customized supply chain solutions for our clients with unified technology systems integrated through a global netwo...
Compliance Ranges Comparison

DHL Express Japan







Expeditors






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

DHL Express Japan

Expeditors
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)