Comparison Overview
Welltower™ Inc. (NYSE:WELL)

Welltower™ Inc. (NYSE:WELL)
United States, US
Last Update: 12/06/2026
Welltower® (NYSE: WELL) provides real estate capital to the world’s leading health and senior care providers to develop the health care infrastructure necessary to keep people well. In everything we do, we believe in revolutionizing the health care system to improve the...

MEB Management Services (Morrison, Ekre & Bart Management Services)
11201 N Tatum Blvd, Phoenix, Arizona, 85028, US
Last Update: 04/04/2026
MEB’S ability to create value for both clients and residents has been the cornerstone of our success. Scott, Libby, Mark, and Jodi have been active in the real estate management industry and have over 125 years of combined experience. With their breadth and depth of kn...
Compliance Ranges Comparison

Welltower™ Inc. (NYSE:WELL)







MEB Management Services (Morrison, Ekre & Bart Management Services)






Benchmark & Cyber Underwriting Signals
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for Welltower™ Inc. (NYSE:WELL) in 2026.
Incidents vs Real Estate Industry Avg (This Year)
No incidents recorded for MEB Management Services (Morrison, Ekre & Bart Management Services) in 2026.
Incident History - Welltower™ Inc. (NYSE:WELL) (X = Date, Y = Severity)
Welltower™ Inc. (NYSE:WELL) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MEB Management Services (Morrison, Ekre & Bart Management Services) (X = Date, Y = Severity)
MEB Management Services (Morrison, Ekre & Bart Management Services) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Welltower™ Inc. (NYSE:WELL)

MEB Management Services (Morrison, Ekre & Bart Management Services)
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.