Comparison Overview
Yara Clean Ammonia

Yara Clean Ammonia
Oslo, NO
Last Update: 19/03/2026
Yara Clean Ammonia (YCA), a subsidiary of Yara International, operates the world's largest ammonia network. With multiple ammonia production and consumption sites across the world, including 15 ships and access to 18 ammonia terminals, we have a significant global prese...

Hapag-Lloyd AG
Ballindamm 25, Hamburg, 20095, DE
Last Update: 11/09/2026
With a fleet of 302 modern container ships and a total transport capacity of 2.5 million TEU, Hapag-Lloyd is one of the world’s leading liner shipping companies. In the Liner Shipping segment, the Company has 15,200 employees and 400 offices in 140 countries. Hapag-Lloy...
Compliance Ranges Comparison

Yara Clean Ammonia







Hapag-Lloyd AG






Benchmark & Cyber Underwriting Signals
Incidents vs Maritime Transportation Industry Avg (This Year)
No incidents recorded for Yara Clean Ammonia in 2026.
Incidents vs Maritime Transportation Industry Avg (This Year)
Hapag-Lloyd AG has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Yara Clean Ammonia (X = Date, Y = Severity)
Yara Clean Ammonia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hapag-Lloyd AG (X = Date, Y = Severity)
Hapag-Lloyd AG cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Yara Clean Ammonia

Hapag-Lloyd AG
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)