Comparison Overview
Deutsche Telekom Investor Relations

Deutsche Telekom Investor Relations
Friedrich-Ebert Allee 140, Bonn, 53113, DE
Last Update: 20/01/2026
Welcome to the official Investor Relations LinkedIn page of Deutsche Telekom! Click "Follow" to keep up-to-date on: 1. Our latest business and financial achievements, 2. Upcoming events and key takeaways, 3. Insightful updates and discussions about Deutsche Telekom's s...

KPN
Wilhelminakade 123, Rotterdam, Zuid-Holland, NL, 3072 AP
Last Update: 07/09/2026
Welkom bij de LinkedIn pagina van KPN. Sinds jaar en dag maakt KPN technologie toegankelijk. Hier leest u alles over de ontwikkelingen rondom de thema’s die KPN belangrijk vindt, zoals Het Nieuwe Leven & Werken, Veiligheid & Privacy en ICT-infrastructuur. Ook een transp...
Compliance Ranges Comparison

Deutsche Telekom Investor Relations







KPN






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Deutsche Telekom Investor Relations in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for KPN in 2026.
Incident History - Deutsche Telekom Investor Relations (X = Date, Y = Severity)
Deutsche Telekom Investor Relations cyber incidents detection timeline including parent company and subsidiaries.
Incident History - KPN (X = Date, Y = Severity)
KPN cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Deutsche Telekom Investor Relations

KPN
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