Comparison Overview
Semperis
Semperis
5 Marine View Plaza, Hoboken, 07030, US
Last Update: 01/03/2026
For security teams charged with defending hybrid and multi-cloud environments, Semperis ensures the integrity and availability of critical enterprise directory services at every step in the cyber kill chain and cuts recovery time by 90%. Purpose-built for securing hybri...
Palo Alto Networks
3000 Tannery Way, SANTA CLARA, 95054, US
Last Update: 15/09/2026
Palo Alto Networks, the global cybersecurity leader, is shaping the cloud-centric future with technology that is transforming the way people and organizations operate. Our mission is to be the cybersecurity partner of choice, protecting our digital way of life. We help ...
Compliance Ranges Comparison
Semperis
Palo Alto Networks
Benchmark & Cyber Underwriting Signals
Incidents vs Computer and Network Security Industry Avg (This Year)
No incidents recorded for Semperis in 2026.
Incidents vs Computer and Network Security Industry Avg (This Year)
Palo Alto Networks has 1162.14% more incidents than the average of all companies with at least one recorded incident.
Incident History - Semperis (X = Date, Y = Severity)
Semperis cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Palo Alto Networks (X = Date, Y = Severity)
Palo Alto Networks cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Semperis
Palo Alto Networks
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