{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-27606 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-27606 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27606 is a medium-severity vulnerability in element-hq element-android, published on 14 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-27606 and fix it if it is affected.\n\nWhat it is: CVE-2025-27606 is a medium-severity vulnerability in element-hq element-android, published on 14 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-27606 in the wild and no public exploit code.\n\nAffected product: element-hq element-android. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-27606/ (Markdown: https://insights.sbomify.com/CVE-2025-27606/index.md)","id":"CVE-2025-27606","markdown":"https://insights.sbomify.com/CVE-2025-27606/index.md","name":"CVE-2025-27606","record":{"aliases":["GHSA-632v-9pm3-m8ch"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Element Android client","requires_auth":"none","summary":"Attackers with physical access can bypass PIN lockout limits to guess credentials and take over accounts in Element Android.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"element","vendor":"element"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-488","name":"Exposure of Data Element to Wrong Session"}],"description":"Element Android is an Android Matrix Client provided by Element. Element Android up to version 1.6.32 can, under certain circumstances, fail to logout the user if they input the wrong PIN more than the configured amount of times. An attacker with physical access to a device can exploit this to guess the PIN. Version 1.6.34 solves the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Element Android PIN autologout bypass","id":"CVE-2025-27606","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Python JSON Logger has a Potential RCE via missing `msgspec-python313-pre` dependency","id":"CVE-2025-27607"},"packages":[],"prev":{"headline":"XWiki Confluence Migrator Pro's homepage is public","id":"CVE-2025-27604"},"products":["element-android"],"published":"2025-03-14","related":[{"cvss_score":8.4,"headline":"Element Android Intent Redirection","id":"CVE-2024-26131","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":6.4,"headline":"Element iOS is vulnerable due to missing decoration for events decrypted with untrusted Megolm sessions","id":"CVE-2022-41904","kev_date_added":null,"published":"2022-11-11"},{"cvss_score":4,"headline":"Element Android can be asked to share internal files.","id":"CVE-2024-26132","kev_date_added":null,"published":"2024-02-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-14","vendors":["element-hq"]},"summary":"Attackers with physical access can bypass PIN lockout limits to guess credentials and take over accounts in Element Android.","url":"https://insights.sbomify.com/CVE-2025-27606/"}