https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 11:01:03 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-343241 EUVD-2026-343241 https://cve.radiocsirt.org/vuln/euvd-2026-343241 https://cve.radiocsirt.org/vuln/fkie_cve-2026-49401 <p>Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7.14, Deno&#39;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.</p> <p>Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7.14, Deno&#39;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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-49401 https://cve.radiocsirt.org/vuln/ghsa-8xpq-cjcf-3wh9 <p><strong>Affected:</strong> crates.io: deno</p> <p>## Summary</p> <p>Deno&#39;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.</p> <p>That means a program could reach a denied path by spelling it differently than the deny rule. For example, with `--deny-read=/secrets/passwörter.txt`, a script could still read the file by opening `/secrets/passwo\u0308rter.txt` (NFD instead of NFC), or `/SECRETS/PASSWÖRTER.txt` (different case, since default APFS volumes are case-insensitive). Other forms include ligature characters (`fi` vs `fi`, `ff` vs `ff`, …) and German `ß` vs `ss`.</p> <p>The denied path and the requested path differed at the byte level, so Deno&#39;s permission check passed; the kernel then resolved them to the same inode and served the file anyway. The same flaw affected `--deny-write`, `--deny-run`, and `--deny-ffi`, which share the same path-comparison code.</p> <p>## Am I affected?</p> <p>You are potentially affected if **all** of the following are true:</p> <p>1. You run Deno on **macOS** (the issue is specific to APFS path-equivalence rules; Linux and Windows are not affected by this variant). 2. You rely on `--deny-read`, `--deny-write`, `--deny-run`, or `--deny-ffi` as a security boundary against less-trusted code — a dependency, plugin, or attacker-controlle…</p> <p><strong>Affected:</strong> crates.io: deno</p> <p>## Summary</p> <p>Deno&#39;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.</p> <p>That means a program could reach a denied path by spelling it differently than the deny rule. For example, with `--deny-read=/secrets/passwörter.txt`, a script could still read the file by opening `/secrets/passwo\u0308rter.txt` (NFD instead of NFC), or `/SECRETS/PASSWÖRTER.txt` (different case, since default APFS volumes are case-insensitive). Other forms include ligature characters (`fi` vs `fi`, `ff` vs `ff`, …) and German `ß` vs `ss`.</p> <p>The denied path and the requested path differed at the byte level, so Deno&#39;s permission check passed; the kernel then resolved them to the same inode and served the file anyway. The same flaw affected `--deny-write`, `--deny-run`, and `--deny-ffi`, which share the same path-comparison code.</p> <p>## Am I affected?</p> <p>You are potentially affected if **all** of the following are true:</p> <p>1. You run Deno on **macOS** (the issue is specific to APFS path-equivalence rules; Linux and Windows are not affected by this variant). 2. You rely on `--deny-read`, `--deny-write`, `--deny-run`, or `--deny-ffi` as a security boundary against less-trusted code — a dependency, plugin, or attacker-controlle…</p> https://cve.radiocsirt.org/vuln/ghsa-8xpq-cjcf-3wh9