CVE-2026-85125Disclosure

LOWCVSS 5.1 · MEDIUM

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

The Android application "YAMAP -Social Trekking GPS App" contains an improper access control vulnerability in its WebView implementation. The in-app browser may cause information leakage from the app or redirect users to unintended websites.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-940

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-09-14: 2Patch / Workaround · 2026-09-14: 1Technical Details · 2026-09-14: 109-14
Signal classification2 categories
Disclosure
150.0%
Patch
150.0%
Referenced assets2 URLs
Full discourse2 posts
  • CVE@CVEnew
    Disclosure

    CVE-2026-85125 The Android application "YAMAP -Social Trekking GPS App" contains an improper access control vulnerability in its WebView implementation. The in-app browser may cause… https://www.cve.org/CVERecord?id=CVE-2026-85125

    Post summary

    The text announces CVE-2026-85125, an improper access control vulnerability in YAMAP app's WebView implementation, providing basic technical classification but no PoC, exploit, or remediation details.

    00000852
    58.1K followersView on X
  • NEXSIGHT@NEXSIGHTNEWS
    Patch

    Android版「YAMAP」にアプリ内ブラウザの脆弱性 — ヤマップはv17.2.0で修正済みと公表、CVE-2026-85125 https://cyber.nexsight.co/articles/2026/09/14/yamap-android-webview-cve-2026-85125-2026-09-14/

    Post summary

    The text announces a vulnerability in the Android version of the YAMAP application, identifying CVE-2026-85125, and highlights that the issue has been patched in version v17.2.0.

    0000085
    70 followersView on X

Explore more