Comparison Overview
Tata Electronics

Tata Electronics
Bengaluru , IN
Last Update: 13/09/2026
Tata Electronics is a prominent global player in the electronics manufacturing industry, with fast-emerging capabilities in Electronics Manufacturing Services, Semiconductor Assembly and Test, Semiconductor Foundry, and Design Services. Established in 2020 as a greenf...

Dabur India Limited
Kaushambi, Sahibabad, Ghaziabad, Uttar Pradesh, IN, 201010
Last Update: 13/09/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

Tata Electronics







Dabur India Limited






Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
Tata Electronics has 20.0% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Dabur India Limited in 2026.
Incident History - Tata Electronics (X = Date, Y = Severity)
Tata Electronics 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

Tata Electronics

Dabur India Limited
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout