Comparison Overview
Empire Express, Inc
Empire Express, Inc
999 Channel Ave, Memphis, Tennessee, US, 38109
Last Update: 06/05/2026
Empire Express, Inc was incorporated May 5, 1985 and has grown over the years to become a strong, respected carrier in the trucking industry. The company is owned by Tim Gatlin, President and CEO, and Ed Gatlin, Founder and Co-owner. Empire serves 48 states and handles...
Swift Transportation
2200 S. 75th Ave, Phoenix, 85043, US
Last Update: 31/03/2026
Swift Transportation is the largest full-truckload motor carrier in North America. Based in Phoenix, Arizona, the Swift terminal network includes over thirty full-service facilities in the United States and Mexico. Swift provides a full line of service solutions, includ...
Compliance Ranges Comparison
Empire Express, Inc
Swift Transportation
Benchmark & Cyber Underwriting Signals
Incidents vs Transportation/Trucking/Railroad Industry Avg (This Year)
Empire Express, Inc has 40.12% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Transportation/Trucking/Railroad Industry Avg (This Year)
No incidents recorded for Swift Transportation in 2026.
Incident History - Empire Express, Inc (X = Date, Y = Severity)
Empire Express, Inc cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Swift Transportation (X = Date, Y = Severity)
Swift Transportation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Empire Express, Inc
Swift Transportation
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.