{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-48546 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-48546 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-48546 is a high-severity code injection vulnerability in lingdojo kana-dojo, published on 11 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-48546 and fix it if it is affected.\n\nWhat it is: CVE-2026-48546 is a high-severity code injection vulnerability in lingdojo kana-dojo, published on 11 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-48546 in the wild and no public exploit code.\n\nAffected product: lingdojo kana-dojo. 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-48546/ (Markdown: https://insights.sbomify.com/CVE-2026-48546/index.md)","id":"CVE-2026-48546","markdown":"https://insights.sbomify.com/CVE-2026-48546/index.md","name":"CVE-2026-48546","record":{"aliases":["GHSA-mq42-j95v-p3gq"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions workflow","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code and escalate privileges by exploiting a sandbox escape in the KanaDojo GitHub Actions workflow via malicious pull requests.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"KanaDojo before 0.1.18 contains a sandbox escape vulnerability that allows an attacker to execute arbitrary code by exploiting the explicit passing of the global require function into a Node.js vm.runInNewContext() sandbox context in the issue-auto-respond.yml workflow. Attackers can submit a pull request modifying messages.cjs to import arbitrary Node.js modules, bypassing sandbox restrictions and achieving remote code execution with full GitHub Actions runner privileges including access to AUTOMATION_PR_TOKEN.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"KanaDojo \u003c 0.1.18 Sandbox Escape RCE via messages.cjs","id":"CVE-2026-48546","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":"KanaDojo \u003c 0.1.18 Command Injection via patchNotesData.json in release.yml","id":"CVE-2026-48547"},"packages":[],"prev":{"headline":"Gradio \u003c 6.15.0 Cookie Injection via Shared Proxy Client","id":"CVE-2026-48545"},"products":["kana-dojo"],"published":"2026-06-11","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["lingdojo"]},"summary":"Attackers can execute arbitrary code and escalate privileges by exploiting a sandbox escape in the KanaDojo GitHub Actions workflow via malicious pull requests.","url":"https://insights.sbomify.com/CVE-2026-48546/"}