{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28211 exists.","fix":"No fix has been published for CVE-2026-28211 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-28211 is a high-severity code injection vulnerability in CyrilleB79 NVDA-Dev-Test-Toolbox, published on 26 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-28211 and fix it if it is affected.\n\nWhat it is: CVE-2026-28211 is a high-severity code injection vulnerability in CyrilleB79 NVDA-Dev-Test-Toolbox, published on 26 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28211 exists.\n\nAffected product: CyrilleB79 NVDA-Dev-Test-Toolbox. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-28211/ (Markdown: https://insights.sbomify.com/CVE-2026-28211/index.md)","id":"CVE-2026-28211","markdown":"https://insights.sbomify.com/CVE-2026-28211/index.md","name":"CVE-2026-28211","record":{"aliases":["GHSA-39pg-6xpm-mjgf"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NVDA accessibility add-on","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into opening malicious log files in the NVDA Dev \u0026 Test Toolbox add-on.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-943","name":"Improper Neutralization of Special Elements in Data Query Logic"}],"description":"The NVDA Dev \u0026 Test Toolbox is an NVDA add-on for gathering tools to help NVDA development and testing. A vulnerability exists in versions 2.0 through 8.0 in the Log Reader feature of this add-on. A maliciously crafted log file can lead to arbitrary code execution when a user reads it with log reader commands. The log reading command process speech log entries in an unsafe manner. Python expressions embedded in the log may be evaluated when when speech entries are read with log reading commands. An attacker can exploit this by convincing a user to open a malicious crafted log file and to analyze it using the log reading commands. When the log is read, attacker-controlled code may execute with the privileges of the current user.\nThis issue does not require elevated privileges and relies solely on user interaction (opening the log file). Version 9.0 contains a fix for the issue. As a workaround, avoid using log reading commands, or at least, commands to move to next/previous log message (any message or commands for each type of message). For more security, one may disable their gestures in the input gesture dialog.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Arbitrary code execution in log reader via untrusted log file","id":"CVE-2026-28211","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Firebird has potential server crash via null pointer dereference when processing op_slice packet","id":"CVE-2026-28212"},"packages":[],"prev":{"headline":"FreePBX: Authenticated SQL Injection in CDR (Call Data Record) Reports","id":"CVE-2026-28210"},"products":["NVDA-Dev-Test-Toolbox"],"published":"2026-02-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-27","vendors":["CyrilleB79"]},"summary":"Attackers can execute arbitrary code by tricking users into opening malicious log files in the NVDA Dev \u0026 Test Toolbox add-on.","url":"https://insights.sbomify.com/CVE-2026-28211/"}