Gepetto S Pizza Restaurant
Last Update: 2026-02-25
Between 750 and 799
None
NAICS: 7225
NAICS Definition: Restaurants and Other Eating Places
Employees: 6
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
Comparison Overview
Gepetto S Pizza Restaurant
VS
Burger King
Burger King
Last Update: 2026-04-01
Between 750 and 799
The year is 1954. Dave and Jim*, two budding entrepreneurs, are on a mission to re-design the perfect broiler, one that will infuse flame-grilled goodness into every burger. And that's how our brand was born. Today the Burger King Corporation, its affiliates and its franchisees collectively operate more than 17,000 restaurants in more than 100 countries and U.S. territories, serving over 11 million guests per day and they’re still coming back for that flame-grilled flavor. The Burger King® brand is owned by Restaurant Brands International Inc. (“RBI”), which owns three of the world’s iconic quick service restaurant brands – Burger King®, Tim Hortons®, and Popeyes Louisiana Kitchen®. But we still have room to grow – and that’s where you come in. We need strong operations, bold marketing, and the best people around to make these brands great. And if we like what we see, there’s no limit to how far you could go here. For more information and exciting career opportunities, please RBI’s website at www.rbicareers.com. For more information about Burger King Corporation, please visit the company’s website at www.bk.com or follow us on Facebook and Twitter. Burger King is a registered trademark of Burger King Corporation. All rights reserved. Please visit www.bk.com for more information on Burger King Corporation trademarks. * Dave Egerton and Jim McLamore, original founders of the Burger King® brand.
NAICS: 7225
NAICS Definition: Restaurants and Other Eating Places
Employees: 126,433
Subsidiaries: 1
12-month incidents
0
Known data breaches
2
Attack type number
3
Compliance Badges Comparison
Security & Compliance Standards Overview
Gepetto S Pizza Restaurant
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Burger King
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Compliance Summary
Gepetto S Pizza Restaurant
100%
Compliance Rate
0/4 Standards Verified
Burger King
0%
Compliance Rate
0/4 Standards Verified
Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Average (This Year)
No incidents recorded for Gepetto S Pizza Restaurant in 2026.
Incidents vs Restaurants Industry Average (This Year)
No incidents recorded for Burger King in 2026.
Incident History — Gepetto S Pizza Restaurant (X = Date, Y = Severity)
Gepetto S Pizza Restaurant cyber incidents detection timeline including parent company and subsidiaries
Incident History — Burger King (X = Date, Y = Severity)
Burger King cyber incidents detection timeline including parent company and subsidiaries
Notable Incidents
Last 3 Security & Risk Events by Company
Gepetto S Pizza Restaurant
Incidents
No Incident
Burger King
Incidents
Date Detected: 9/2025
Type:Breach
Attack Vector: Hard-coded Credentials, Plain-text Passwords in Emails, Unrestricted API Access, Default/Weak Passwords (e.g., 'admin')
Motivation: Ethical Hacking / Responsible Disclosure
Blog: Blog
Date Detected: 7/2025
Type:Vulnerability
Attack Vector: Weak Default Credentials, Insecure Direct Object Reference (IDOR)
Blog: Blog
FAQ
Burger King company demonstrates a stronger AI Cybersecurity Score compared to Gepetto S Pizza Restaurant company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.
Burger King company has historically faced a number of disclosed cyber incidents, whereas Gepetto S Pizza Restaurant company has not reported any.
In the current year, Burger King company and Gepetto S Pizza Restaurant company have not reported any cyber incidents.
Neither Burger King company nor Gepetto S Pizza Restaurant company has reported experiencing a ransomware attack publicly.
Burger King company has disclosed at least one data breach, while Gepetto S Pizza Restaurant company has not reported such incidents publicly.
Neither Burger King company nor Gepetto S Pizza Restaurant company has reported experiencing targeted cyberattacks publicly.
Burger King company has disclosed at least one vulnerability, while Gepetto S Pizza Restaurant company has not reported such incidents publicly.
Neither Gepetto S Pizza Restaurant nor Burger King holds any compliance certifications.
Neither company holds any compliance certifications.
Burger King company has more subsidiaries worldwide compared to Gepetto S Pizza Restaurant company.
Burger King company employs more people globally than Gepetto S Pizza Restaurant company, reflecting its scale as a Restaurants.
Neither Gepetto S Pizza Restaurant nor Burger King holds SOC 2 Type 1 certification.
Neither Gepetto S Pizza Restaurant nor Burger King holds SOC 2 Type 2 certification.
Neither Gepetto S Pizza Restaurant nor Burger King holds ISO 27001 certification.
Neither Gepetto S Pizza Restaurant nor Burger King holds PCI DSS certification.
Neither Gepetto S Pizza Restaurant nor Burger King holds HIPAA certification.
Neither Gepetto S Pizza Restaurant nor Burger King holds GDPR certification.
Latest Global CVEs (Not Company-Specific)
Description
nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.
Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Description
PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.
Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Description
PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description
PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description
PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
