Threema Apps Shine in External Audit

18 person-days, four apps, zero significant vulnerabilities. An independent audit by Assured Security Consultants confirms that the Threema mobile apps deliver on their security promises.

Security is not a static state. It is an ongoing process. That’s why we have independent experts review Threema on a regular basis, most recently Assured Security Consultants. Their verdict is clear: “The application reflects a high standard of security and privacy, highlighting the team’s strong commitment to secure development.”

“We’re delighted with the clear result, which confirms that regular internal reviews and the extra effort we put into development pay off.”

Danilo Bargen, Chief Technology Officer at Threema

How was the audit conducted?

The experts at Assured audited the Threema apps for Android and iOS, covering both Threema Private and Threema Work. The audit required 18 person-days of work, spread over three weeks in September and October 2026.

OWASP’s Mobile Application Security Verification Standard (MASVS) served as the basis for the audit. This standard provides developers and security professionals with a benchmark for app security and is also designed to serve as a reference when procuring applications.

The experts combined automated analysis, dynamic testing, and manual code review, supplemented by an LLM-assisted code audit.

What was found?

The audit found no critical, high, or medium vulnerabilities. Assured notes: “Against the MASVS baseline, the application shows strong controls in the STORAGE and CRYPTO domains.”

The experts classified one finding as low risk. This will be fixed with version 6.7.0 of the Android app, which is scheduled for December.

The report also contains three “notes,” two of which (3.2 and 3.4) have already been addressed in the current app versions. Regarding the third (3.3), we are retaining the current implementation as it reflects a deliberate design decision. The proposed change would be less efficient and would break backward compatibility. However, if we ever redesign the cryptographic architecture, we will revisit this decision.

You can find all the details in the audit report: