Comparison Overview
Forward Air Corporation

Forward Air Corporation
P.O. Box 1058, Greeneville, Tennessee, US, 37744
Last Update: 01/04/2026
Forward Air has been a leader in the expedited ground transportation industry for over 40 years. Our portfolio of services has evolved to meet each customer’s unique shipping needs, including expedited linehaul (TL & LTL), pick-up and delivery, intermodal drayage, pool ...

Transport for NSW
Multiple locations , Multiple locations across the state, AU
Last Update: 03/04/2026
We’re an innovative NSW government organisation comprised of a network of agencies and divisions that keep the state moving. Our focus is on delivering safe, reliable and integrated transport networks for everyone. With over 28,000 team members, we’re committed to incl...
Compliance Ranges Comparison

Forward Air Corporation







Transport for NSW






Benchmark & Cyber Underwriting Signals
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for Forward Air Corporation in 2026.
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for Transport for NSW in 2026.
Incident History - Forward Air Corporation (X = Date, Y = Severity)
Forward Air Corporation cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Transport for NSW (X = Date, Y = Severity)
Transport for NSW cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Forward Air Corporation

Transport for NSW
FAQ
Latest Global CVEs
In OpenStack Designate before 22.0.2, the mDNS handler performs pool-blind lookups when resolving record queries and NOTIFY requests. When two zones with the same name exist across different pools, the lookup fails with a deterministic error, causing the handler to return REFUSED for all DNS queries through that path. The _handle_notify path is exploitable via a single unauthenticated UDP packet. This is independently reachable through the cross-tenant zone overlap described in a different recent CVE, and also affects legitimate same-tenant cross-pool configurations. BIND9 views do not mitigate this issue as mDNS is a shared service upstream of any view configuration.
In OpenStack Designate before 22.0.1, zone creation checks (_is_subzone, _is_superzone, and the duplicate-zone DB constraint) are scoped to the target pool only. An authenticated user can bypass these checks by scheduling a zone to a different pool via the AttributeFilter scheduler, creating an overlapping zone that conflicts with another tenant's zone. This enables cross-tenant DNS hijack (redirecting traffic to attacker-controlled IPs) and DNS denial of service (NODATA responses). Exploitation requires a multi-pool deployment with AttributeFilter enabled in scheduler_filters, which is a non-default but documented and supported configuration for self-service tiering.
UpSnap is a wake on lan web app. Versions prior to 5.4.0 have an OS command injection vulnerability in the UpSnap’s device management functionality due to the presence of unsafe shell command template interpolation using the ip and the mac fields. User-controlled values can be inserted into the wake_cmd and shutdown_cmd templates and executed via /bin/sh -c (Linux) or cmd /C (Windows) without sanitization, resulting in an authenticated Remote Code Execution (RCE). A low-privileged user with permission to create or edit devices can execute arbitrary operating system commands on the UpSnap hosted server. Version 5.4.0 patches the issue.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. When `secureEnabled=true`, FUXA `1.3.0-2773` still allows guest and invalid-token requests to read project, alarms, and scheduler APIs. Version 1.3.1 fixes this issue.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In fuxa-server version 1.3.0, the GET /api/project endpoint exposes sensitive project configuration data to guest-context requests even when secureEnabled is enabled. Version 1.3.1 fixes the issue.