
An independent security audit of Threema’s Android and iOS apps found one weakness in the Android biometric app lock but no critical vulnerabilities.
Threema says the fix is scheduled for December in Android version 6.7.0.
Assured Security Consultants’ Jimmie Rudvall and Wictor Olsson spent 18 person-days reviewing the Android and iOS editions of Threema Private and Threema Work between September 14 and October 2, 2026. They used OWASP’s Mobile Application Security Verification Standard as a baseline, combining automated scans, runtime testing, and manual code review. The auditors manually verified every finding surfaced with help from a large language model.
Threema is a Swiss messaging service that offers end-to-end encryption for messages, calls, and media. Threema Private is its consumer app, while Threema Work is aimed at businesses and public-sector organizations.
How the biometric lock works
Assured found that Threema’s Android app lock relies on a success signal from the operating system’s biometric prompt. In a modified environment, an attacker who could manipulate how the app runs might be able to unlock it without a valid biometric check. Assured rated the risk as low and recommended tying successful biometric verification to a cryptographic operation backed by the Android Keystore.
The auditors rated the apps’ storage and cryptography controls highly. They highlighted Android’s use of SQLCipher to encrypt local data and iOS’s use of the Keychain to protect cryptographic keys and identity credentials. They also noted privacy controls that hide sensitive content in notifications and widgets.
Threema keeps its file encryption design
One of the audit’s three informational findings concerned how Threema encrypts uploaded files and photos. The app uses fixed values known as nonces alongside a fresh random 256-bit key for each encryption operation.
Assured said the fresh keys prevent the usual nonce-reuse problem in normal operation and recommended randomizing the nonce as an extra safeguard. Threema says the change would reduce efficiency and break backward compatibility. It will revisit the decision if it redesigns its cryptography.
Assured marked the other two notes as resolved. One concerned known flaws in Rust dependencies that Threema said were used only in a test tool and excluded from production builds. The other concerned a potential script injection issue in an iOS settings screen. Assured found no way for an attacker to supply input to the affected code in the shipped app and verified that Threema rewrote it to remove the unsafe pattern.







Leave a Reply