Comparison Overview
Taco Bell ONEUROPE (UK & Europe)

Taco Bell ONEUROPE (UK & Europe)
N/A
Last Update: 02/04/2026
Born and raised in California since 1962, Taco Bell has journeyed from being a local favourite for Crunchy Tacos on the West Coast to establishing itself as a global phenomenon. With a remarkable presence spanning over 8,200 restaurants, 350 franchise organizations, and...

Raising Cane's Chicken Fingers
6800 Bishop Rd, Plano, 75024, US
Last Update: 05/04/2026
Founded by Todd Graves in 1996 in Baton Rouge, La., RAISING CANE'S CHICKEN FINGERS has over 800 restaurants in 41 states, with many new restaurants under construction. The company has ONE LOVE®—craveable chicken finger meals—and is continually recognized for its unique ...
Compliance Ranges Comparison

Taco Bell ONEUROPE (UK & Europe)







Raising Cane's Chicken Fingers






Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Taco Bell ONEUROPE (UK & Europe) in 2026.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Raising Cane's Chicken Fingers in 2026.
Incident History - Taco Bell ONEUROPE (UK & Europe) (X = Date, Y = Severity)
Taco Bell ONEUROPE (UK & Europe) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Raising Cane's Chicken Fingers (X = Date, Y = Severity)
Raising Cane's Chicken Fingers cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Taco Bell ONEUROPE (UK & Europe)

Raising Cane's Chicken Fingers
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.