# Deno.env.toObject() ignores the variables listed in --deny-env and returns all environment variables

Advisory record · `GHSA-7w8p-chxq-2789`

- **Identifiers:** `GHSA-7w8p-chxq-2789` · `CVE-2025-48934`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-201](https://cwe.mitre.org/data/definitions/201.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 4 Jun 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Jun 2025, 21:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `deno` (crates.io): affected `<2.1.13 || >=2.2.0, <2.2.13`; fixed in `2.1.13`, `2.2.13`
- `deno_runtime` (crates.io): affected `<0.212.0`; fixed in `0.212.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Deno versions before 2.1.13, and from 2.2.0 before 2.2.13, and the deno_runtime crate before 0.212.0 are affected. Deno.env.toObject() returns all environment variables even when they are listed in --deny-env, so code run with that flag can still read secrets it was meant to be blocked from. Upgrade deno to 2.1.13 or 2.2.13, or deno_runtime to 0.212.0.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.5 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0044, the 39th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:17 UTC: First seen by agentprime
- 31 Oct 2026, 15:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7w8p-chxq-2789)

## Sources

- [GitHub Advisory Database: GHSA-7w8p-chxq-2789](https://github.com/advisories/GHSA-7w8p-chxq-2789)
- [OSV: GHSA-7w8p-chxq-2789](https://osv.dev/vulnerability/GHSA-7w8p-chxq-2789)
- <https://github.com/denoland/deno/security/advisories/GHSA-7w8p-chxq-2789>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-48934>
- <https://github.com/denoland/deno/pull/29079>
- <https://github.com/denoland/deno/commit/2959e083912420988066a001c2b2d6732a1b562f>
- <https://github.com/denoland/deno/commit/946ccda1aa19a00c478a5e6826b75053b050d753>
- <https://docs.deno.com/api/deno/~/Deno.Env.toObject>
- <https://docs.deno.com/runtime/fundamentals/security/#environment-variables>
- <https://github.com/denoland/deno>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-7w8p-chxq-2789>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7w8p-chxq-2789/>. Everything for agents: <https://agentprime.io/llms.txt>.
