Comparison Overview
Instituto Global para la Excelencia del Cuidado de la Salud-Keralty. IGEC-K

Instituto Global para la Excelencia del Cuidado de la Salud-Keralty. IGEC-K
Calle 127 N° 20-56, Bogota, Bogota, CO, 11101
Last Update: 27/11/2025
The IGEK Global Institute of Keralty Excellence was born on September 8, 2018 as a technical-scientific instance of the Presidency of Health and Innovation that works from a technical-scientific approach to contribute to care with high standards of excellence, which im...

Purpose Brands, LLC
111 Weir Drive, Woodbury, 55125, US
Last Update: 29/03/2026
Purpose Brands, LLC provides fitness, nutrition and wellness support and services to more than 7,000 communities and millions of people around the world. We own and operate the world’s largest and most trusted portfolio of fitness, health and wellness franchise brand...
Compliance Ranges Comparison

Instituto Global para la Excelencia del Cuidado de la Salud-Keralty. IGEC-K







Purpose Brands, LLC






Benchmark & Cyber Underwriting Signals
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Instituto Global para la Excelencia del Cuidado de la Salud-Keralty. IGEC-K in 2026.
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Purpose Brands, LLC in 2026.
Incident History - Instituto Global para la Excelencia del Cuidado de la Salud-Keralty. IGEC-K (X = Date, Y = Severity)
Instituto Global para la Excelencia del Cuidado de la Salud-Keralty. IGEC-K cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Purpose Brands, LLC (X = Date, Y = Severity)
Purpose Brands, LLC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Instituto Global para la Excelencia del Cuidado de la Salud-Keralty. IGEC-K

Purpose Brands, LLC
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.