{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-32888 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-32888 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32888 is a high-severity vulnerability in n/a, published on 1 May 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-32888 and fix it if it is affected.\n\nWhat it is: CVE-2025-32888 is a high-severity vulnerability in n/a, published on 1 May 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-32888 in the wild and no public exploit code.\n\nAffected product: n/a. 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-32888/ (Markdown: https://insights.sbomify.com/CVE-2025-32888/index.md)","id":"CVE-2025-32888","markdown":"https://insights.sbomify.com/CVE-2025-32888/index.md","name":"CVE-2025-32888","record":{"aliases":["GHSA-jqgh-w22q-m24f"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"goTenna Mesh app","requires_auth":"none","summary":"Attackers can exploit hardcoded verification tokens in the goTenna Mesh app to bypass SMS sending restrictions.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gotenna","vendor":"gotenna"},{"product":"mesh_firmware","vendor":"gotenna"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:L/A:H/C:L/I:L/PR:N/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered on goTenna Mesh devices with app 5.5.3 and firmware 1.1.12. The verification token used for sending SMS through a goTenna server is hardcoded in the app.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-32888","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5.","id":"CVE-2025-32889"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-32887"},"products":["n/a"],"published":"2025-05-01","related":[{"cvss_score":7.3,"headline":"An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5.","id":"CVE-2025-32889","kev_date_added":null,"published":"2025-05-01"},{"cvss_score":7.1,"headline":"Information disclosure in n/a","id":"CVE-2025-32887","kev_date_added":null,"published":"2025-05-01"},{"cvss_score":7.1,"headline":"goTenna Pro ATAK Plugin Use of Cryptographically Weak Pseudo-Random Number Generator","id":"CVE-2024-45723","kev_date_added":null,"published":"2024-09-26"},{"cvss_score":6.5,"headline":"Other in n/a","id":"CVE-2025-32885","kev_date_added":null,"published":"2025-05-01"},{"cvss_score":6,"headline":"goTenna Pro ATAK Plugin Weak Authentication","id":"CVE-2024-41722","kev_date_added":null,"published":"2024-09-26"},{"cvss_score":6,"headline":"goTenna Pro ATAK Plugin Missing Support for Integrity Check","id":"CVE-2024-43108","kev_date_added":null,"published":"2024-09-26"}],"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":"total"},"state":"PUBLISHED","updated":"2025-05-01","vendors":["n/a"]},"summary":"Attackers can exploit hardcoded verification tokens in the goTenna Mesh app to bypass SMS sending restrictions.","url":"https://insights.sbomify.com/CVE-2025-32888/"}