dbcve.org
AnkiApplication · Ankitects

CVE-2025-62186

HIGH · 7.8 CVSS v3.1 Published 2025-10-07
Fix available
A fix is available. Upgrade to 25.02.5 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
Ankitects Anki before 25.02.5 allows a crafted shared deck on Windows to execute arbitrary commands when playing audio because of URL scheme mishandling.

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

Ankitects Anki before version 25.02.5 contains a vulnerability where a maliciously crafted shared deck can execute arbitrary commands on Windows systems through improper URL scheme handling when audio files are played. The audio playback functionality processes URL schemes without adequate validation, allowing an attacker to trigger command execution.

MitigationUpgrade Anki to version 25.02.5 or later. Until upgraded, avoid importing or opening shared decks from untrusted sources on Windows systems.

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
AnkiApplication
Affected:< 25.02.5

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. Verify Anki is installed on Windows
    Check for Anki executable in common installation paths such as C:\Program Files\Anki\anki.exe or C:\Users\<username>\AppData\Local\Programs\anki\anki.exe. Alternatively, open Command Prompt and run: where anki
    Affected if Anki is found installed on a Windows system
  2. Determine installed Anki version
    Launch Anki and navigate to Help > About, or run: anki --version in Command Prompt. The version number displayed is your installed version.
    Affected if The displayed version is any version prior to 25.02.5 (for example, 25.02.4, 25.02.3, 24.x, etc.)
  3. Confirm Windows is the operating system
    Open Command Prompt and run: systeminfo | findstr /B /C:"OS Name" or check System Properties. The vulnerability specifically affects Windows systems.
    Affected if The operating system is Windows and the previous version check shows a vulnerable version
  4. Assess audio playback usage context
    Review whether Anki is used with media files, particularly if importing or opening shared decks from external sources. The vulnerability triggers when playing audio files within a deck.
    Affected if Audio files are played in Anki on a vulnerable Windows installation (the attack vector is through malicious audio file URLs)

You are affected if Anki is installed on a Windows system with a version lower than 25.02.5 and audio playback from potentially untrusted decks is used.

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

Upgrade Anki to version 25.02.5 or later. Until upgraded, avoid importing or opening shared decks from untrusted sources on Windows systems.

Recommended fix High confidence

Anki 25.02.5 or later

  1. Check the current installed version of Anki by opening the application and navigating to Help > About
  2. Visit the official Anki downloads page at https://github.com/ankitects/anki/releases or the official Anki website
  3. Download Anki version 25.02.5 or later for Windows
  4. Close Anki completely if it is running
  5. Install the downloaded version, overwriting the existing installation
  6. Restart Anki and verify the version by checking Help > About to confirm version 25.02.5 or later is installed
  7. Be cautious when importing shared decks from untrusted sources, as they may contain malicious content

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

Fix this in Anki Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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