Yandex BrowserApplication · Yandex

CVE-2021-25254

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-21
Fix available
A fix is available. Upgrade to 21.1.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Yandex Browser Lite for Android before 21.1.0 allows remote attackers to spoof the address bar.

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 · high confidence

This is an address bar spoofing vulnerability in Yandex Browser Lite for Android versions prior to 21.1.0. Attackers can manipulate the browser to display a fraudulent URL in the address bar while actually rendering malicious content, enabling phishing attacks. The CVSS 5.3 indicates low attack complexity with no authentication required but limited impact scope.

MitigationUpdate Yandex Browser Lite for Android to version 21.1.0 or later. If updates are not immediately possible, advise users to avoid entering sensitive information while using the affected browser and implement browser deployment controls to restrict usage of unpatched versions.

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
Yandex BrowserApplication
Affected:< 21.1.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

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

  1. Identify if Yandex Browser Lite is installed
    Check the device or mobile device management (MDM) inventory for applications named 'Yandex Browser Lite' or 'Яндекс.Браузер Лайт' on Android devices
    Affected if Yandex Browser Lite for Android is present on any device in the organization
  2. Locate the installed version number
    On Android, go to Settings > Apps > Yandex Browser Lite > App info, or query via ADB: 'adb shell dumpsys package com.yandex.browser.lite'
    Affected if Unable to retrieve version information or version field shows unknown
  3. Compare installed version against affected range
    Check if the installed version is less than 21.1.0. Version format is typically major.minor.patch (e.g., 21.0.3, 20.9.5)
    Affected if Installed version is below 21.1.0 (e.g., 21.0.x, 20.x.x, or any version number less than 21.1.0)
  4. Verify the browser handles URL display
    Manual test: navigate to a known website and observe if the address bar correctly displays the URL being loaded. The vulnerability allows spoofed URLs to appear in the address bar
    Affected if The address bar displays a different URL than the one actually being loaded in the page content

A user is affected if Yandex Browser Lite for Android is installed with a version number less than 21.1.0, as this version range contains the address bar spoofing vulnerability.

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.

dbcve · scoped
Upgrade available Upgrade to 21.1.0 or later
Fixed in 21.1.0
Interim mitigation

Update Yandex Browser Lite for Android to version 21.1.0 or later. If updates are not immediately possible, advise users to avoid entering sensitive information while using the affected browser and implement browser deployment controls to restrict usage of unpatched versions.

Recommended fix Moderate confidence

21.1.0 or later

  1. Open the Google Play Store or Yandex's official app distribution channel
  2. Check the current version of Yandex Browser Lite for Android installed on the device
  3. Update Yandex Browser Lite for Android to version 21.1.0 or later
  4. Verify the update was successful by checking the app version after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Yandex Browser Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-25254 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-25254 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