dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-12189

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
Zero-click

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 · unedited
A flaw has been found in Moovit Bus & Public Transit App 1.18 on Android. This affects an unknown part of the component com.tranzmate. Executing a manipulation can lead to improper authorization in handler for custom url scheme. The attack can only be executed locally. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 confidence

The Moovit Bus & Public Transit App version 1.18 for Android contains an improper authorization vulnerability in the custom URL scheme handler within the com.tranzmate component. A local attacker can manipulate the URL scheme handler to bypass authorization controls and access protected functionality that should require proper authentication or authorization checks.

MitigationSince the vendor has not responded to disclosure, users should limit local device access by avoiding installation of untrusted applications and monitor for unauthorized access. A professional security assessment and patch development would require reverse-engineering the app to identify and remediate the flawed authorization logic in the URL scheme handler.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Moovit app is installed
    On the Android device, check installed applications for 'Moovit' or 'Tranzmate' branded apps. Use 'adb shell pm list packages' or check Settings > Apps.
    Affected if The Moovit Bus & Public Transit App or tranzmate component is installed on the device
  2. Determine installed Moovit version
    Check the app version in Play Store, app info screen (Settings > Apps > Moovit > Version), or via 'adb shell dumpsys package <package_name>'
    Affected if The installed version matches 1.18 or falls within the affected version range around 1.18
  3. Verify com.tranzmate component exists
    Use 'adb shell pm list packages' to find packages containing 'tranzmate', or inspect app manifest for the com.tranzmate component.
    Affected if The com.tranzmate component is present and exposed in the application
  4. Confirm custom URL scheme is registered
    Decompile the APK (if available) and inspect AndroidManifest.xml for intent-filter entries with custom URL schemes (e.g., moovit://, tranzmate://).
    Affected if A custom URL scheme handler is registered without proper authorization guards in the intent-filter
  5. Check for potentially malicious local apps
    Audit installed applications for suspicious apps that may have permission to invoke URL schemes, particularly those requesting ACTIVITY recognition or with broad intent permissions.
    Affected if Untrusted or suspicious applications with capability to trigger custom URL schemes are installed on the same device

A user is affected if Moovit app version 1.18 (or nearby versions with the same vulnerability) with the com.tranzmate component is installed and a potentially malicious app on the same device can invoke its unprotected custom URL scheme.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor has not responded to disclosure, users should limit local device access by avoiding installation of untrusted applications and monitor for unauthorized access. A professional security assessment and patch development would require reverse-engineering the app to identify and remediate the flawed authorization logic in the URL scheme handler.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12189 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12189 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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