Comparison Overview
USAL

USAL
21021 Essman Lane, Houston, Texas 77073, US
Last Update: 10/07/2026
USAL is the premier auto transport and logistics provider. Headquartered in Houston, TX, USAL offers safe, on-time, legally-compliant, and damage-free delivery to its customers through its brand of companies—USAL Solutions, a national brokerage and logistics provider, a...

J.B. Hunt Transport Services, Inc.
615 J.B Hunt Corporate Drive, Lowell, 72745, US
Last Update: 13/09/2026
J.B. Hunt specializes in freight shipping for customers of all sizes. Our mission is to drive long-term value for our people, customers and shareholders while staying focused on our vision to create the most efficient transportation network in North America. Our foundat...
Compliance Ranges Comparison

USAL







J.B. Hunt Transport Services, Inc.






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

USAL

J.B. Hunt Transport Services, Inc.
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.