Comparison Overview
Meghna Group of Industries (MGI)

Meghna Group of Industries (MGI)
MGI Head Office, Fresh Villa. Road 34 House 15, Gulshan-1, 1212, BD
Last Update: 04/04/2026
MGI represents an enterprise and brand with 48 years of national and global experience. It currently operates more than 54 industrial units, houses over 50,000 employees, 6,650 distributors, and 15,000 suppliers under its umbrella, and achieves an annual turnover of app...

Dabur India Limited
Kaushambi, Sahibabad, Ghaziabad, Uttar Pradesh, IN, 201010
Last Update: 01/04/2026
We are Dabur, an Indian Transnational offering the best nature-based solutions to provide holistic Health & Well-Being to households in more than 120 markets spanning Asia, Europe and The US. A world leader in Ayurveda, we are a family of over 7,000 individuals continuo...
Compliance Ranges Comparison

Meghna Group of Industries (MGI)







Dabur India Limited






Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Meghna Group of Industries (MGI) in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Dabur India Limited in 2026.
Incident History - Meghna Group of Industries (MGI) (X = Date, Y = Severity)
Meghna Group of Industries (MGI) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dabur India Limited (X = Date, Y = Severity)
Dabur India Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Meghna Group of Industries (MGI)

Dabur India Limited
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.