Comparison Overview
Sapp Bros., Inc.
Sapp Bros., Inc.
9915 SOUTH 148TH STREET, OMAHA, 68138, US
Last Update: 02/04/2026
Sapp Bros., Inc. is a collection of 18 full-service, friendly travel centers; primarily located on Interstate-80 from as far west as Toquerville, Utah to Clearfield, Pennsylvania in the east. Sapp Bros. is also a leading petroleum wholesale distributor with a robust off...
UPS
55 Glenlake Parkway, NE, Atlanta, 30328, US
Last Update: 15/09/2026
Operating in more than 200 countries and territories, we’re committed to moving our world forward by delivering what matters. Beginning as a small messenger service, UPS was started by two enterprising teenagers and a $100 loan. Now, we’re almost 500,000 UPSers strong, ...
Compliance Ranges Comparison
Sapp Bros., Inc.
UPS
Benchmark & Cyber Underwriting Signals
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for Sapp Bros., Inc. in 2026.
Incidents vs Truck Transportation Industry Avg (This Year)
UPS has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Sapp Bros., Inc. (X = Date, Y = Severity)
Sapp Bros., Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - UPS (X = Date, Y = Severity)
UPS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sapp Bros., Inc.
UPS
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.