Comparison Overview
YRC Freight
YRC Freight
10990 Roe Avenue, Overland Park, KS, US, 66211
Last Update: 02/04/2026
YRC Freight, a leading transporter of industrial, commercial and retail goods, specializes in less-than-truckload (LTL) shipping solutions for businesses. Based in Overland Park, Kan., YRC Freight provides comprehensive North American coverage and offers a broad portfol...
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
YRC Freight
J.B. Hunt Transport Services, Inc.
Benchmark & Cyber Underwriting Signals
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for YRC Freight in 2026.
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for J.B. Hunt Transport Services, Inc. in 2026.
Incident History - YRC Freight (X = Date, Y = Severity)
YRC Freight 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
YRC Freight
J.B. Hunt Transport Services, Inc.
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout