Comparison Overview
Lindt & Sprüngli Brasil

Lindt & Sprüngli Brasil
Rua Professor Atílio Innocenti 165, São Paulo, São Paulo, 04538-000, BR
Last Update: 24/12/2025
A Lindt & Sprüngli é reconhecida no mercado como líder em chocolate premium. A marca possui mais de 175 anos e oferecemos uma ampla seleção de produtos em mais de 120 países ao redor do mundo. Nossos chocolates são produzidos em 12 fábricas da Lindt na Europa e nos Esta...

Seara
Avenida Marginal Direita do Tietê 500, São Paulo, SP, BR, 05118100
Last Update: 28/03/2026
Presente há mais de 65 anos nos lares brasileiros, a Seara tem um dos portfólios mais diversificados do setor de alimentos - com opções que vão de proteína animal (frango e suínos) a pratos prontos, margarinas, pizzas, frios, lanches prontos, embutidos e proteína vegeta...
Compliance Ranges Comparison

Lindt & Sprüngli Brasil







Seara






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

Lindt & Sprüngli Brasil

Seara
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.