Comparison Overview
McDonald's Philippines (Golden Arches Development Corporation)
McDonald's Philippines (Golden Arches Development Corporation)
17th Floor Citibank Center Building, Makati, undefined, 1226, PH
Last Update: 16/03/2026
The world famous Golden Arches arrived in the Philippines in 1981 when Dr. George T. Yang opened the first-ever McDonald’s restaurant in the country. The historic restaurant still stands on its original location in Morayta, Manila. In 1992, McDonald’s brought its world...
Panda Restaurant Group
1683 Walnut Grove Ave, Rosemead, 91770, US
Last Update: 01/04/2026
Panda Restaurant Group is the global leader in Asian dining and includes Panda Express, Panda Inn, and more. Founded in 1973 by Andrew and Peggy Cherng, we are a family-owned business with more than 2,600 restaurants worldwide. Our mission is to deliver exceptional Asia...
Compliance Ranges Comparison
McDonald's Philippines (Golden Arches Development Corporation)
Panda Restaurant Group
Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for McDonald's Philippines (Golden Arches Development Corporation) in 2026.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Panda Restaurant Group in 2026.
Incident History - McDonald's Philippines (Golden Arches Development Corporation) (X = Date, Y = Severity)
McDonald's Philippines (Golden Arches Development Corporation) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Panda Restaurant Group (X = Date, Y = Severity)
Panda Restaurant Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
McDonald's Philippines (Golden Arches Development Corporation)
Panda Restaurant Group
FAQ
Latest Global CVEs
A vulnerability was identified in Databend up to 1.2.881 on HTTP. This affects the function ClientSessionManager::state_key of the file src/query/service/src/servers/http/v1/session/client_session_manager.rs of the component Tenant Handler. The manipulation leads to authorization bypass. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The pull request to fix this issue awaits acceptance.
A vulnerability was determined in VoltAgent up to 2.1.17. Affected by this issue is the function handleGetMemoryConversation of the file packages/server-core/src/handlers/memory.handlers.ts of the component Memory REST API. Executing a manipulation of the argument conversationId can lead to improper authorization. The attack may be performed from remote. This attack is characterized by high complexity. The exploitation is known to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
A vulnerability was found in SimStudioAI sim up to 0.6.92. Affected by this vulnerability is an unknown functionality in the library apps/sim/lib/core/security/deployment.ts of the component Password Protection Handler. Performing a manipulation results in use of weak hash. The attack is possible to be carried out remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The exploit has been made public and could be used. The pull request to fix this issue awaits acceptance.
A vulnerability has been found in RAGapp up to 0.1.5. Affected is the function FileHandler.upload_file/FileHandler.remove_file of the file src/ragapp/backend/controllers/files.py of the component Knowledge File Handler. Such manipulation leads to path traversal. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.
A flaw has been found in khoj-ai khoj up to 2.0.0-beta.28. This impacts an unknown function of the file src/khoj/routers/api_chat.py of the component Conversation Sharing Handler. This manipulation of the argument conversation.agent causes incorrect authorization. Remote exploitation of the attack is possible. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.