Comparison Overview
Sparkasse Schwaben-Bodensee

Sparkasse Schwaben-Bodensee
St.-Josefs-Kirchplatz 6-8, Memmingen, 87700, DE
Last Update: 02/04/2026
Die Sparkasse Schwaben-Bodensee übernimmt Verantwortung für Menschen in allen Lebensphasen. Mit nachhaltigen Lösungen für ihre Region und einer Bandbreite an Finanzdienstleistungen bietet sie innovative Möglichkeiten für ihre Privat-, Unternehmens- und kommunalen Kunden...

TMF Group
Luna ArenA, Herikerbergweg 238, , Amsterdam , North Holland, NL, 1101 CM
Last Update: 13/09/2026
We provide employee, financial and legal administration so that firms can invest and operate safely around the world. TMF Group is a single global team with over 11,000 colleagues in more than 125 offices across 87 jurisdictions, covering 92% of world GDP and 95% of F...
Compliance Ranges Comparison

Sparkasse Schwaben-Bodensee







TMF Group






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Sparkasse Schwaben-Bodensee in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for TMF Group in 2026.
Incident History - Sparkasse Schwaben-Bodensee (X = Date, Y = Severity)
Sparkasse Schwaben-Bodensee cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TMF Group (X = Date, Y = Severity)
TMF Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sparkasse Schwaben-Bodensee

TMF Group
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)