CVE-2025-32889
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5. The verification token used for sending SMS through a goTenna server is hardcoded in the app.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe goTenna v1 mobile app (version 5.5.3) contains a hardcoded verification token that is used to authenticate SMS sending requests to goTenna servers. This hardcoded credential allows anyone who discovers the token to send SMS messages through the affected goTenna infrastructure without proper user authorization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.25.5= 5.5.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify goTenna mobile application versionOn iOS, go to Settings > goTenna > Version. On Android, go to Settings > Apps > goTenna > Version info. Alternatively, check the APK package details or app listing in the app store.Affected if The installed version equals 5.5.3 exactly
-
Identify Gotenna Mesh Firmware versionOpen the goTenna Mesh app, navigate to Settings > About > Device Info, or check the firmware version displayed on the device display when powered on.Affected if The firmware version equals 0.25.5 exactly
-
Determine if application binary has been modified or repackagedCompare the installed APK or IPA hash against the official build from goTenna's official app store listing. Use tools to verify code signature validity.Affected if The application binary differs from the official build or fails signature verification
-
Check for exposed API endpoints using the application tokenIf you operate backend services that interface with goTenna, monitor authentication logs for requests using static tokens rather than dynamic session credentials. Review API access logs for patterns consistent with token-based SMS requests.Affected if SMS authentication requests use a static token rather than user-specific dynamic credentials
You are affected if you have goTenna mobile app version 5.5.3 or Gotenna Mesh Firmware version 0.25.5 installed, or if your environment accepts the hardcoded token for SMS authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace the hardcoded verification token with a proper dynamic authentication mechanism (such as OAuth tokens, JWT, or per-session credentials) and implement server-side validation. Issue a security update for both the app and firmware to revoke the compromised token and implement the new authentication flow.
- Consultation8.0 h
- Implementation32.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $17,920.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32889 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32889 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data