Comparison Overview
Ivanti

Ivanti
10377 South Jordan Gateway, South Jordan, 84095, US
Last Update: 24/07/2026
Ivanti is a global enterprise IT and security software company that provides the trusted data authority for AI-driven, autonomous endpoint management. Ivanti connects IT and security operations data in a unified system of record –– giving teams clear visibility of every...

IGT
6355 S Buffalo Dr, Las Vegas, NV, US, 89113
Last Update: 15/09/2026
IGT is a leading global provider of gaming, digital and financial technology solutions, formed through the combination of International Game Technology PLC’s Gaming & Digital Business and Everi Holdings Inc. IGT’s offering spans gaming machines, game content and systems...
Compliance Ranges Comparison

Ivanti







IGT






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
Ivanti has 1126.42% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for IGT in 2026.
Incident History - Ivanti (X = Date, Y = Severity)
Ivanti cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IGT (X = Date, Y = Severity)
IGT cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Ivanti

IGT
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