Comparison Overview
Have I Been Pwned
Have I Been Pwned
The Interent, Surfers Paradise, 4217, AU
Last Update: 15/09/2026
Have I Been Pwned (HIBP) is a free data breach search and notification service. The service has been used by tens of millions of people to search through billions of breached records and supports tens of thousands of visitors a day. HIBP aggregates data that's been exp...
Infosys
Infosys Limited, Bangalore, Karnataka, IN, 560100
Last Update: 07/09/2026
Infosys is a global leader in next-generation digital services and consulting. We enable clients in more than 50 countries to navigate their digital transformation. With over three decades of experience in managing the systems and workings of global enterprises, we expe...
Compliance Ranges Comparison
Have I Been Pwned
Infosys
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Have I Been Pwned has 235.57% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Infosys in 2026.
Incident History - Have I Been Pwned (X = Date, Y = Severity)
Have I Been Pwned cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Infosys (X = Date, Y = Severity)
Infosys cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Have I Been Pwned
Infosys
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