CVE-2025-21615
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 · uneditedAAT (Another Activity Tracker) is a GPS-tracking application for tracking sportive activities, with emphasis on cycling. Versions lower than v1.26 of AAT are vulnerable to data exfiltration from malicious apps installed on the same device.
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 confidenceAAT versions prior to 1.26 improperly protect stored GPS tracking data, allowing malicious applications installed on the same Android device to access sensitive location and activity data through insecure data storage, exported components, or improper file permissions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Confirm AAT application is installedCheck for the presence of the AAT app on the Android device using the package manager: `pm list packages | grep aat` or view installed applications in Settings > AppsAffected if The AAT application is present on the device
-
Retrieve installed AAT versionObtain the version name and version code of AAT using `dumpsys package <package_name>` or through the device Settings > Apps > AAT > App infoAffected if Unable to determine the version, or version is returned but cannot be compared
-
Compare version against affected thresholdCompare the installed version to 1.26 - note that versions prior to 1.26 (e.g., 1.25, 1.24.x, etc.) are affected; versions 1.26 and later are notAffected if Installed version is a numeric value less than 1.26 (e.g., 1.25.0, 1.24, 1.20)
-
Identify storage exposure indicatorsReview app permissions and exported components via `dumpsys package -a <package_name>` - look for flags indicating android:exported="true" on components that handle location data, or verify if shared storage directories exist with overly permissive permissions (world-readable)Affected if Exported components are found that handle location/activity data without proper protection, or storage directories show world-readable permissions
The device is affected if AAT is installed with any version prior to 1.26, as the app stores GPS tracking data without adequate protection against access by other malicious apps on the same device.
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.
dbcve · scopedUpgrade to AAT v1.26 or later, which contains proper data protection mechanisms. Until upgraded, avoid installing untrusted apps on devices running vulnerable AAT versions.
v1.26
- 1. Identify the current installed version of AAT (Another Activity Tracker) on the device
- 2. Navigate to the official application store where AAT is distributed (Google Play Store, Apple App Store, or the app's official download page)
- 3. Check for available updates for the AAT application
- 4. Update the application to version v1.26 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21615 — 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-21615 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