Comparison Overview
Primary Connect

Primary Connect
Woolworths, Bella Vista, New South Wales, 2153, AU
Last Update: 28/03/2026
Primary Connect moves products all over Australia and New Zealand, and we’re passionate about doing it in the safest, freshest way possible. We opened in Australia in 2003 and New Zealand in 2009. Since then, we’ve grown to be a successful ‘freight and logistics busin...

Penske Logistics
2675 Morgantown Rd, Reading, 19607, US
Last Update: 14/09/2026
Penske Logistics is a Penske Transportation Solutions company headquartered in Reading, Pennsylvania. The company is a leading provider of innovative supply chain and logistics solutions. Penske offers solutions including dedicated transportation, distribution center ma...
Compliance Ranges Comparison

Primary Connect







Penske Logistics






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

Primary Connect

Penske Logistics
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)