Comparison Overview
Llano Logistics

Llano Logistics
N/A
Last Update: 24/03/2026

Yellow
501 Commerce St. Suite, 1120, Nashville, 37203, US
Last Update: 13/09/2026
Yellow, a Fortune 500 company headquartered in Nashville, TN is one of the largest super-regional less-than-truckload (LTL) companies in North America. Nearly 100 years ago, Yellow created the LTL industry, and now it comprises four successful regional LTL companies and...
Compliance Ranges Comparison

Llano Logistics







Yellow






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

Llano Logistics

Yellow
FAQ
Latest Global CVEs
Authorization Bypass Through User-Controlled Key vulnerability in Ultimate Member Ultimate Member ultimate-member allows Privilege Escalation.This issue affects Ultimate Member: from n/a through 2.13.1.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Unlimited Elements Unlimited Elements For Elementor (Free Widgets, Addons, Templates) unlimited-elements-for-elementor allows Reflected XSS.This issue affects Unlimited Elements For Elementor (Free Widgets, Addons, Templates): from n/a through 2.0.20.
Improper Validation of Specified Quantity in Input vulnerability in Themeum Kirki kirki allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Kirki: from n/a through 6.3.1.
OpenAM before 16.1.3 contains a server-side request forgery vulnerability that allows attackers able to register or modify OAuth 2.0 clients to make OpenAM fetch internal resources via an unvalidated jwks_uri. Attackers can trigger unauthenticated fetches through client-authentication and ID-token validation to probe internal hosts, metadata endpoints or local files, or exhaust request threads for denial of service.
OpenAM before 16.1.3 contains an improper authorization vulnerability that allows delegated administrators to destroy sessions outside their realms because realm checks use the requester's realm. Authenticated accounts holding the iplanet-am-session-destroy-sessions attribute can supply a target session identifier or handle to forcibly log out users in any realm.