Comparison Overview
PHOENIX CONTACT Smart Business GmbH

PHOENIX CONTACT Smart Business GmbH
Zionskirchstraße 73a, Berlin, 10119, DE
Last Update: 29/04/2026
𝐓𝐡𝐢𝐬 𝐢𝐬 𝐲𝐨𝐮𝐫 𝐭𝐢𝐜𝐤𝐞𝐭 𝐭𝐨 𝐢𝐧𝐝𝐮𝐬𝐭𝐫𝐢𝐚𝐥 𝐈𝐨𝐓 - 𝐒𝐦𝐚𝐫𝐭 𝐒𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐫𝐮𝐧 𝐨𝐧 𝐭𝐡𝐞 𝐏𝐫𝐨𝐟𝐢𝐜𝐥𝐨𝐮𝐝.𝐢𝐨 𝐜𝐨𝐮𝐥𝐝 𝐩𝐥𝐚𝐭𝐟𝐨𝐫𝐦. Our scalable, standardised cloud services are easy to run - tailored to the industrial requireme...

Neobpo
Rua Pais Leme, 14, São Paulo, SP, BR, 05424-010
Last Update: 04/09/2026
Somos especializados em integrar tecnologia com inteligência humana, oferecendo soluções digitais que promovem transformação e eficiência operacional. Nosso foco é gerar valor por meio de resultados reais, utilizando inteligência digital para atender às necessidades esp...
Compliance Ranges Comparison

PHOENIX CONTACT Smart Business GmbH







Neobpo






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for PHOENIX CONTACT Smart Business GmbH in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Neobpo in 2026.
Incident History - PHOENIX CONTACT Smart Business GmbH (X = Date, Y = Severity)
PHOENIX CONTACT Smart Business GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Neobpo (X = Date, Y = Severity)
Neobpo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

PHOENIX CONTACT Smart Business GmbH

Neobpo
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