Comparison Overview
Tyson Foodservice

Tyson Foodservice
P.O. Box 2020 (CP581), Springdale, US
Last Update: 29/11/2025
We are committed to you, your operation and your customers’ needs. We’re here to help by providing market-relevant content and innovative solutions.

JBS
Avenida Marginal Direita do Tietê, 500, São Paulo, 05118-100, BR
Last Update: 11/09/2026
Na JBS, a gente alimenta um futuro melhor. Tudo começou com uma pequena porta de um açougue, há mais de 70 anos. E, daquela porta, surgiram muitas outras. Foi acreditando em coisas simples, em fazer sempre melhor, contando com o trabalho de muita gente e abrindo portas...
Compliance Ranges Comparison

Tyson Foodservice







JBS






Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Tyson Foodservice in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for JBS in 2026.
Incident History - Tyson Foodservice (X = Date, Y = Severity)
Tyson Foodservice cyber incidents detection timeline including parent company and subsidiaries.
Incident History - JBS (X = Date, Y = Severity)
JBS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Tyson Foodservice

JBS
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.