Vulnerabilities in pkg:npm/ses

PACKAGE
Advisory Identifier: GHSA-h9w6-f932-gq62
Share
Advisory Summary

CVE-2025-32792 is a HIGH ses's global contour bindings leak vulnerability (CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere) affecting Ses libraries in the npm ecosystem. The issue involves ses's global contour bindings leak into compartment lexical scope. Remediation is available by upgrading affected packages to version 1.12.0.

4 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/ses

4 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/ses. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-h9w6-f932-gq62 CVE-2025-32792 HIGH ses's global contour bindings leak into Compartment lexical scope
GHSA-9c4h-3f7h-322r CVE-2023-39532 CRITICAL SES's dynamic import and spread operator provides possible path to arbitrary exfiltration and execution
GHSA-whpx-q3rq-w8jc - LOW Hardening of TypedArrays with non-canonical numeric property names in SES
GHSA-6jg8-7333-554w - CRITICAL Sandbox Breakout in realms-shim

CVE-2025-32792 at a Glance

CVE Identifier CVE-2025-32792
GHSA Identifier GHSA-h9w6-f932-gq62
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere
Affected Product Ses
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2025-32792

To remediate this vulnerability, upgrade all affected Ses dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

ses fixed: 1.12.0 
npm install ses@1.12.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls ses

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-32792, inspect your project dependencies using npm:

npm ls ses

Analyze the terminal output to locate any version of Ses in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.12.0), your application is affected.

Note: The npm ls ses command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere, where the product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does. In Ses, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Web pages and web extensions using `ses` and the `Compartment` API to evaluate third-party code in an isolated execution environment that have also elsewhere used `const`, `let`, and `class` bindings in the top-level scope of a `<script>` tag will have inadvertently revealed these bindings in the lexical scope of third-party code. ### Patches This compromise is addressed in `ses` version `1.12.0`. The mechanism for confining third-party code involves a `with` block and a semi-opaque scope `Proxy`. The proxy previously revealed any named property to the surrounding lexical scope if it were absent on `globalThis`, so that the third-party code would receive an informative `ReferenceError`, relying on the invalid assumption that only properties of `globalThis` are in the top-level lexical scope. The solution makes the scope proxy fully opaque. Consequently, accessing an unbound free lexical name will produce `undefined` instead of throwing `ReferenceError`. Assigning to an unbound free lexical name will continue to throw a `ReferenceError`. ### Workarounds This problem can be mitigated either by avoiding top-level `let`, `const`, or `class` bindings in `<script>` tags, which is an existing industry best-practice, or change these to `var` bindings to be reflected on `globalThis`, or upgrade `ses` to version `1.12.0` or greater. Some bundlers by default transform top-level `let`, `const`, and `class` bindings to `var`. ### Disclosure This vulnerability was disclosed by @mingijunggrape in the course of their studies at UNIST (Ulsan National Institute of Science and Technology) as a member of the Web Security Lab (https://websec-lab.github.io/).

CVE-2025-32792 Affected Ses Versions

1 component(s)
Fixed Versions:
1.12.0
Product / Package Ecosystem Affected Versions Fixed Version
ses
npm/ses
npm
< 1.12.0
1.12.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/endojs/endo/security/advisories/GHSA-h9w6-f932-gq62
NVD — CVE-2025-32792 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-32792
Ses Source Repository REPOSITORY
https://github.com/endojs/endo

Frequently Asked Questions

What is CVE-2025-32792?
CVE-2025-32792 is a security vulnerability in Ses involving ses's global contour bindings leak into Compartment lexical scope under CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere.
Which Ses versions are affected?
Affected versions include releases prior to 1.12.0 across affected packages: ses.
What version fixes CVE-2025-32792?
Upgrading to 1.12.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is ses affected?
Yes, ses is affected in releases prior to 1.12.0. Upgrade your dependency to 1.12.0 or later.
What CWE is associated with CVE-2025-32792?
CVE-2025-32792 is classified under CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere (The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.).
How can I check npm dependencies for CVE-2025-32792?
Run the dependency tree command: 'npm ls ses'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-h9w6-f932-gq62",
  "modified" : "2025-04-18T18:34:51Z",
  "published" : "2025-04-18T15:10:05Z",
  "aliases" : [ "CVE-2025-32792" ],
  "summary" : "ses's global contour bindings leak into Compartment lexical scope",
  "details" : "### Impact\n\nWeb pages and web extensions using `ses` and the `Compartment` API to evaluate third-party code in an isolated execution environment that have also elsewhere used `const`, `let`, and `class` bindings in the top-level scope of a `<script>` tag will have inadvertently revealed these bindings in the lexical scope of third-party code.\n\n### Patches\n\nThis compromise is addressed in `ses` version `1.12.0`. The mechanism for confining third-party code involves a `with` block and a semi-opaque scope `Proxy`. The proxy previously revealed any named property to the surrounding lexical scope if it were absent on `globalThis`, so that the third-party code would receive an informative `ReferenceError`, relying on the invalid assumption that only properties of `globalThis` are in the top-level lexical scope. The solution makes the scope proxy fully opaque. Consequently, accessing an unbound free lexical name will produce `undefined` instead of throwing `ReferenceError`.\nAssigning to an unbound free lexical name will continue to throw a `ReferenceError`.\n\n### Workarounds\n\nThis problem can be mitigated either by avoiding top-level `let`, `const`, or `class` bindings in `<script>` tags, which is an existing industry best-practice, or change these to `var` bindings to be reflected on `globalThis`, or upgrade `ses` to version `1.12.0` or greater.\n\nSome bundlers by default transform top-level `let`, `const`, and `class` bindings to `var`.\n\n### Disclosure\n\nThis vulnerability was disclosed by @mingijunggrape in the course of their studies at UNIST (Ulsan National Institute of Science and Technology) as a member of the Web Security Lab (https://websec-lab.github.io/).",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "ses"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.12.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/endojs/endo/security/advisories/GHSA-h9w6-f932-gq62"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-32792"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/endojs/endo"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-497" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-04-18T15:10:05Z",
    "nvd_published_at" : "2025-04-18T16:15:23Z"
  }
}