Hardening of TypedArrays with non-canonical numeric property names in SES

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact What kind of vulnerability is it? Who is impacted? In Hardened JavaScript, programs can harden objects to safely share objects with co-tenant programs without risk of these other programs tampering with their API surface. Hardening does not guarantee that objects are pure or immutable, so a hardened Map, for example is superficially tamper-proof, but any party holding a reference to the object can both read and write its contents. Based on this precedent, and because TypedArray instances cannot be frozen with Object.isFrozen, harden does not freeze TypedArrays and instead makes them non-extensible and makes all non-indexed properties non-writable and non-configurable. This is consistent with the treatment of Map because the indexed properties represent mutable content and non-indexed properties represent the API. Due to a defect in harden, properties that have names that parse as numbers but are not the same as the canonical representation of those numbers, as in "+0" and ""…

Published by the source

20 Oct 2022, 18:38 UTC

Last modified by the source

9 Jan 2023, 05:07 UTC

Source last checked

26 Oct 2026, 12:16 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-whpx-q3rq-w8jc

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-whpx-q3rq-w8jc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-whpx-q3rq-w8jc

Advisory: Hardening of TypedArrays with non-canonical numeric property names in SES
IDs: GHSA-whpx-q3rq-w8jc
Record: https://patchnext.com/advisories/ghsa-whpx-q3rq-w8jc (revision 2, source checked 26 Oct 2026, 12:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ses 0.16.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm ses: affected < 0.16.0; fixed in 0.16.0

## Suggested inspection (read-only)
- `npm ls ses --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ses.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-whpx-q3rq-w8jc (OSV record GHSA-whpx-q3rq-w8jc lists affected ranges: npm ses >=0 <0.16.0 (fixed))
- Verified: https://github.com/advisories/GHSA-whpx-q3rq-w8jc (GitHub-reviewed advisory GHSA-whpx-q3rq-w8jc lists affected ranges: npm ses >=0 <0.16.0)

Commands are suggestions: review each one before running it.