Anki
CVE-2025-62186
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPublish malicious shared deck online
-
ExploitVictim downloads and imports deck
-
ExecutionAudio playback triggers URL scheme mishandling
-
ImpactExecute arbitrary commands as user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Trusted source inclusion only
|
| Exploitation Conditions | Exploitation requires three concrete conditions confirmed by the vendor release notes: (1) the Anki client must be running on Windows - other platforms are not affected; (2) the victim must obtain and import an attacker-crafted SHARED DECK; and (3) the deck's audio must be played, at which point mishandling of a URL scheme leads to command execution. Limiting factors that reduce realistic risk: the attack is local (AV:L), depends on the user voluntarily acquiring a malicious third-party deck and triggering audio playback (user interaction), and is confined to Anki versions before 25.02.5. The related 25.02.5 hardening - prompting for permission before opening external app links (e.g. obsidian://) - indicates untrusted URL schemes are the core abuse surface. |
| Impact | The input CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N) yields a 7.8 'High' base score driven by full C/I/A compromise from arbitrary command execution. However, the metrics conflict with the described attack: command execution occurs only when a victim obtains a malicious SHARED DECK and plays its audio, which in practice requires user interaction (UI:R) and no pre-existing privileges on the target (PR:N) rather than PR:L/UI:N - so the official vector appears to overstate autonomy and understate the user-interaction dependency. Real-world risk signals are modest and consistent with each other: EPSS is 0.14% (3rd percentile), the CVE is NOT on CISA KEV, and no public exploit code was identified in the provided data. The local attack vector plus the social-engineering prerequisite (downloading and importing an attacker-supplied deck, then triggering audio playback) make this a user-interaction-gated, Windows-only issue rather than a remotely-wormable or mass-exploitable flaw. Net assessment: a genuinely high-impact (RCE) but low-likelihood issue - worth patching promptly on Windows installs that import third-party decks, but not an emergency relative to network-exploitable critical bugs. Note the input 'Information Disclosure' tag contradicts the arbitrary-command-execution nature of the flaw (CWE-829, untrusted functionality) and should be treated with caution. |
| Exploit ScenarioDerived | An attacker publishes a malicious shared Anki deck to a community sharing site; a Windows user downloads and imports it. When the deck plays an audio file, Anki mishandles a crafted URL scheme and executes attacker-controlled OS commands in the user's context. No public proof-of-concept was identified at the time of analysis, and the local attack vector plus required deck import/audio playback make this a social-engineering-dependent attack. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Arbitrary command execution in Anki versions before 25.02.5 on Windows occurs when a victim imports a crafted shared deck and plays its audio, which triggers mishandling of a URL scheme and lets attacker-controlled payloads run with the user's privileges. Exploitation is local and depends on the user voluntarily obtaining and importing a malicious third-party deck and triggering audio playback (user interaction), and it is confined to Windows clients; the authoritative assessment scores it 7.8 High, reflecting full confidentiality, integrity and availability impact. No public exploit code has been identified at time of analysis, and the EPSS score is only 0.14% (3rd percentile), consistent with the social-engineering prerequisite rather than opportunistic scanning.
RemediationAI
Vendor-released patch: 25.02.5 - upgrade Anki on Windows to 25.02.5 or later, available from https://github.com/ankitects/anki/releases/tag/25.02.5, which contains the fix for the audio-playback command execution hole plus the new prompt requesting permission before opening external app links. If immediate upgrade is not possible, treat every shared deck as untrusted: disable or restrict import of third-party .apkg decks (only import decks you authored or obtained from a verified source) and avoid playing audio contained in untrusted decks, accepting that this degrades normal study workflows - note that audio files used for language learning are frequently embedded in shared decks, so this mitigation breaks legitimate card playback. Additionally, limit the blast radius by running Anki as a standard, non-administrative user; restrict or remove unnecessary custom URL scheme handlers registered under HKCU\Software\Classes (for example obsidian:// or other consumer app schemes) so a malicious scheme cannot resolve to an installed handler - the trade-off is that legitimate deep links from other applications stop working. Application allowlisting via Windows Defender Application Control or AppLocker can block unexpected child processes spawned from Anki, though it requires tuning to avoid blocking legitimate media players. Note that EPSS is low (0.14%) and no public exploit code has been identified at time of analysis, so prioritize the upgrade over emergency isolation, but treat deck provenance as a continuing supply-chain risk given the CWE-829 root cause.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is classified as CWE-829 (Inclusion of Functionality from Untrusted Control Sphere): Anki incorporates a control sphere (a shared deck's media/link content) that it does not validate against trusted sources, and on Windows that untrusted content is handed to the operating system's URL scheme resolution path during audio playback. When a deck's audio entry or its associated link is resolved, Anki passes the scheme to the OS shell instead of confining it, so a crafted scheme (a registered application handler, or another app link such as obsidian://) is invoked and the associated command runs. The affected component is the Anki desktop client for the ankitects:anki package, captured by CPE cpe:2.3:a:ankitects:anki:*:*:*:*:*:*:*:* with all builds before 25.02.5 vulnerable; the release notes for 25.02.5 describe two related fixes - plugging the audio-playback command execution hole and adding a permission prompt before opening external app links (e.g. obsidian://) - confirming that untrusted URL schemes are the core abuse surface. The input vector (AV:L/AC:L/PR:L/UI:N) and the authoritative assessment vector (AV:L/AC:L/PR:N/UI:R) agree on a local, low-complexity attack resulting in complete loss of confidentiality, integrity and availability; both require local execution context, with the assessment emphasizing that no prior privileges are needed (PR:N) but that user interaction (importing the deck and playing audio) is required.
Know when Anki gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack is local and file/deck-based (AV:L) and requires the victim to import a deck and play audio (UI:R, PR:N); arbitrary command execution grants full C/I/A impact.
Primary rating from NVD.
CVSS VectorNVD
DescriptionNVD
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.
Executive ViewAI
Anki, the desktop flashcard application widely used for study and professional training, contains a Windows-only flaw that allows a malicious shared deck to execute attacker-controlled code with the victim's own permissions once the imported deck's audio is played. Because a user must deliberately obtain and import an untrusted third-party deck, the realistic threat is targeted social engineering rather than opportunistic, automated attack - but a successful compromise would grant the attacker the same access as that user, including any corporate data, credentials, or network resources reachable from the workstation. Leadership should treat this as a user-targeting risk on Windows endpoints that host Anki, not a broad infrastructure exposure.
No vendor-released patch identified at time of analysis. Interim mitigations: prohibit import and playback of shared or third-party .apkg decks from untrusted sources; quarantine deck attachments at email and web gateways; enforce least privilege and remove local administrator rights for Anki users; restrict or monitor the application's registered URL scheme handlers; validate all deck imports from a known-good source before playback; apply application allowlisting and endpoint detection to flag anomalous child processes spawned by Anki; retain Windows-specific scope in mind, as non-Windows clients are reportedly unaffected.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Affected Products (CPE)NVD
An arbitrary script execution vulnerability exists in the MPV functionality of Ankitects Anki 24.04. Rated high severity
An reflected XSS vulnerability exists in the handling of invalid paths in the Flask server in Ankitects Anki 24.04. Rate
An vulnerability in the handling of Latex exists in Ankitects Anki 24.04. Rated medium severity (CVSS 6.5), this vulnera
A blocklist bypass vulnerability exists in the LaTeX functionality of Ankitects Anki 24.04. Rated medium severity (CVSS
Arbitrary code execution in Anki versions before 25.02.5 allows a crafted shared deck to drop a malicious executable nam
Arbitrary file read and exfiltration in Anki prior to 25.09.4 allows a remote attacker to access sensitive files on a vi
An issue was discovered in Ankitects Anki through 25.02. Rated medium severity (CVSS 6.1), this vulnerability is remotel
Anki versions before 25.02.6 fail to confine media filenames referenced by sound/video tags to the media folder, so a cr
Cross-origin request forgery against Anki's local HTTP server allows a malicious website to trigger unauthorized side-ef
NVD
CVE.org
EPSS
GitHub
Exploit-DB