Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-qq26-84mh-26j9 | Deno's --deny-read check does not prevent permission bypass |
Thu, 16 Oct 2025 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:deno:deno:*:*:*:*:*:*:*:* |
Wed, 08 Oct 2025 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 08 Oct 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Deno
Deno deno |
|
| Vendors & Products |
Deno
Deno deno |
Wed, 08 Oct 2025 01:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Deno is a JavaScript, TypeScript, and WebAssembly runtime. In versions prior to 2.5.3 and 2.2.15, `Deno.FsFile.prototype.stat` and `Deno.FsFile.prototype.statSync` are not limited by the permission model check `--deny-read=./`. It's possible to retrieve stats from files that the user do not have explicit read access to (the script is executed with `--deny-read=./`). Similar APIs like `Deno.stat` and `Deno.statSync` require `allow-read` permission, however, when a file is opened, even with file-write only flags and deny-read permission, it's still possible to retrieve file stats, and thus bypass the permission model. Versions 2.5.3 and 2.2.15 fix the issue. | |
| Title | Deno's --deny-read check does not prevent permission bypass | |
| Weaknesses | CWE-269 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-10-08T18:54:33.415Z
Reserved: 2025-09-30T19:43:49.903Z
Link: CVE-2025-61786
Updated: 2025-10-08T18:54:28.851Z
Status : Analyzed
Published: 2025-10-08T01:15:33.010
Modified: 2025-10-16T18:13:38.117
Link: CVE-2025-61786
No data.
OpenCVE Enrichment
Updated: 2025-10-08T13:35:11Z
Github GHSA