Sogexia Android App Compile Affected SDK v35, Max SDK 32 and fixed in v36, was discovered to contain hardcoded
Source GCVE Database
Not known to be exploited · CVSS 9.1 Critical.
Data as of 13 Nov 2026, 18:30 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
AI-suggested
Upgrade to SDK version 36 or later where the hardcoded encryption keys issue has been resolved. Since this is a software vulnerability fixed in a specific SDK version, applying the official fix is the recommended remediation.
Description
The Sogexia Android app, compiled with SDK version 35 and targeting a maximum SDK of 32, contained hardcoded encryption keys within the encryption_helper.dart file. This vulnerability was addressed in SDK version 36. The flaw allows an attacker to potentially compromise the confidentiality and integrity of encrypted data due to exposed cryptographic keys.