{"answers":{"affected":"2 open source packages ship an affected version, including deno. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-49401 in the wild and no public exploit code.","fix":"Upgrade deno to 2.7.14 or later.","what":"CVE-2026-49401 is a high-severity vulnerability in denoland deno, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-49401 and fix it if it is affected.\n\nWhat it is: CVE-2026-49401 is a high-severity vulnerability in denoland deno, published on 23 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-49401 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- deno (crates.io): affected all versions; fixed in 2.7.14\n- deno (crates.io): affected all versions; fixed in 2.7.14\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-49401/ (Markdown: https://insights.sbomify.com/CVE-2026-49401/index.md)","id":"CVE-2026-49401","markdown":"https://insights.sbomify.com/CVE-2026-49401/index.md","name":"CVE-2026-49401","record":{"aliases":["GHSA-8xpq-cjcf-3wh9","JLSEC-2026-655"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Deno runtime","requires_auth":"low_privilege","summary":"Attackers can bypass Deno's filesystem and execution permission restrictions on macOS by exploiting Unicode normalization mismatches in path comparisons.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"deno","vendor":"deno"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-41","name":"Improper Resolution of Path Equivalence"},{"id":"CWE-176","name":"Improper Handling of Unicode Encoding"}],"description":"Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7.14, Deno's permission system enforces filesystem and execution restrictions by comparing the requested path against the path supplied to --deny-read, --deny-write, --deny-run, or --deny-ffi. On macOS, that comparison was done at the raw-byte level while the APFS filesystem treats different Unicode spellings of the same name as the same file. That means a program could reach a denied path by spelling it differently than the deny rule. This vulnerability is fixed in 2.7.14.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Deno Permission Bypass via Unicode Normalization Mismatch on macOS (APFS)","id":"CVE-2026-49401","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Deno: Command Injection via spawnSync \u0026 spawn on Windows","id":"CVE-2026-49402"},"packages":[{"ecosystem":"crates.io","fixed":["2.7.14"],"introduced":["0"],"last_affected":[],"package":"deno","purl":null,"source":"GHSA-8xpq-cjcf-3wh9"},{"ecosystem":"crates.io","fixed":["2.7.14"],"introduced":["0"],"last_affected":[],"package":"deno","purl":"pkg:cargo/deno","source":"GHSA-8xpq-cjcf-3wh9"}],"prev":{"headline":"October CMS: PHP Object Injection via Backend Widget Session Storage","id":"CVE-2026-49400"},"products":["deno"],"published":"2026-06-23","related":[{"cvss_score":10,"headline":"Deno improperly handles resizable ArrayBuffer","id":"CVE-2023-28445","kev_date_added":null,"published":"2023-03-23"},{"cvss_score":10,"headline":"Sandbox bypass leading to arbitrary code execution in Deno","id":"CVE-2022-24783","kev_date_added":null,"published":"2022-03-25"},{"cvss_score":9.8,"headline":"Static imports inside dynamically imported modules do not adhere to permission checks","id":"CVE-2021-32619","kev_date_added":null,"published":"2021-05-28"},{"cvss_score":9.2,"headline":"Deno node:crypto doesn't finalize cipher","id":"CVE-2026-22863","kev_date_added":null,"published":"2026-01-15"},{"cvss_score":8.8,"headline":"Deno interactive permission prompt spoofing via improper ANSI stripping","id":"CVE-2024-27936","kev_date_added":null,"published":"2024-03-06"},{"cvss_score":8.8,"headline":"Deno is vulnerable to interactive `run` permission prompt spoofing via improper ANSI neutralization","id":"CVE-2023-28446","kev_date_added":null,"published":"2023-03-24"},{"cvss_score":8.6,"headline":"Deno missing \"--allow-net\" permission check for built-in Node modules","id":"CVE-2023-33966","kev_date_added":null,"published":"2023-05-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-07-31","vendors":["denoland"]},"summary":"Attackers can bypass Deno's filesystem and execution permission restrictions on macOS by exploiting Unicode normalization mismatches in path comparisons.","url":"https://insights.sbomify.com/CVE-2026-49401/"}