dbcve.org
Yandex BrowserApplication · Yandex

CVE-2022-28226

HIGH · 7.8 CVSS v3.1 Published 2022-06-15
Fix available
A fix is available. Upgrade to 22.3.3.801 or later.
See remediation →
80/100
Remediation priority · High
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
Local privilege vulnerability in Yandex Browser for Windows prior to 22.3.3.801 allows a local, low privileged, attacker to execute arbitary code with the SYSTEM privileges through manipulating temporary files in directory with insecure permissions during Yandex Browser update process.

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

Yandex Browser for Windows versions prior to 22.3.3.801 contains a local privilege escalation vulnerability where insecure file permissions on temporary files used during the browser update process allow a low-privileged local attacker to manipulate these files and execute arbitrary code with SYSTEM-level privileges.

MitigationUpdate Yandex Browser to version 22.3.3.801 or later, which addresses the insecure temporary file permissions in the update mechanism.

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:< 22.3.3.801

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Locate Yandex Browser installation
    Check for Yandex Browser in typical installation paths such as C:\Program Files\Yandex\YandexBrowser\ or C:\Users\%USERNAME%\AppData\Local\Yandex\YandexBrowser\. Also check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for an entry named 'Yandex'.
    Affected if Yandex Browser is found on the system
  2. Identify installed version
    Right-click the browser executable (typically named Application\browser.exe within the installation folder), select Properties, and view the File Version information. Alternatively, check the Windows Registry value 'DisplayVersion' under the Yandex uninstall registry key.
    Affected if The version shown is lower than 22.3.3.801
  3. Verify update mechanism configuration (optional context)
    Examine the update configuration files in the Yandex Browser user data directory (typically under %LOCALAPPDATA%\Yandex\YandexBrowser\Update\ or similar) for file permissions on temporary update files. Use icacls or a file permission audit tool to check if low-privileged users have write access to these files.
    Affected if Temporary update files are writable by non-admin users (indicates the vulnerable configuration)

A user is affected if Yandex Browser version 22.3.3.801 or higher is NOT installed on their Windows system.

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 22.3.3.801 or later
Fixed in 22.3.3.801
Interim mitigation

Update Yandex Browser to version 22.3.3.801 or later, which addresses the insecure temporary file permissions in the update mechanism.

Recommended fix Moderate confidence

22.3.3.801 or later (latest stable release)

  1. Open Yandex Browser and navigate to the menu (three dots) > Help > About Yandex Browser to check the current version
  2. If the version is older than 22.3.3.801, download the latest version of Yandex Browser from the official website at https://browser.yandex.com
  3. Close all running instances of Yandex Browser
  4. Run the downloaded installer to update Yandex Browser to version 22.3.3.801 or later
  5. After installation, verify the version again via Help > About Yandex Browser to confirm the update was successful
Caveat Minimal risk; browser upgrades may occasionally affect extension compatibility or saved settings, but user data is typically preserved

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

Fix this in Yandex Browser Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28226 — 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-2022-28226 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