Comparison Overview
MSD Türkiye

MSD Türkiye
Levent 199 Ofis Bloğu, İstanbul, undefined, undefined, TR
Last Update: 19/03/2026
Ürünlerimizle ilgili yan etki & kalite şikayetlerini lütfen sosyal medya hesaplarımıza değil, https://www.msd.com.tr/iletisim-formlari/'na bildirin. MSD olarak, 130 yılı aşkın süredir hayatları kurtarma ve iyileştirme misyonu ile dünyanın en zorlu hastalıkları için ila...

MANKIND PHARMA LTD
Phase 3, New Delhi, IN
Last Update: 06/09/2026
Mankind Pharma, one of the top 5 leading pharmaceutical companies in India, started its journey in 1995. Today, we have an employee base of over 20,000 and are racing towards $1 Billion. At Mankind, we aspire to aid the community in leading a healthy life by formulating...
Compliance Ranges Comparison

MSD Türkiye







MANKIND PHARMA LTD






Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for MSD Türkiye in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for MANKIND PHARMA LTD in 2026.
Incident History - MSD Türkiye (X = Date, Y = Severity)
MSD Türkiye cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MANKIND PHARMA LTD (X = Date, Y = Severity)
MANKIND PHARMA LTD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

MSD Türkiye

MANKIND PHARMA LTD
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)