Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

ag-psd: Uncontrolled Memory Allocation in PSD Layer Decoding (totalMemoryLimit bypass)

CVE-2026-63501GHSA-6w3r-6hpr-hp6p

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (ag-psd 31.0.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm ag-psd

    Affected
    < 31.0.1
    Fixed in
    31.0.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-63501: 0.51% estimated exploitation activity in the next 30 days; percentile 43.83 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The `readPsd()` function in `ag-psd` accepts a `totalMemoryLimit` option to cap memory usage when parsing untrusted PSD files, but this limit is never forwarded to the layer image buffer allocation path. A property name mismatch (`totalMemoryLimit` vs. `memoryLimit`) causes the size guard inside `createImageDataBitDepth` to be skipped unconditionally. An attacker who can supply a crafted PSD to any application using `ag-psd` for server-side parsing can force an unbounded heap allocation — a 5000×5000 layer in a 86-byte file allocates 200 MB — leading to denial of service through process memory exhaustion regardless of what limit the caller specified.

Details `readPsd()` (exported from `src/index.ts:22`) wraps caller-supplied bytes in a `PsdReader` object that inherits `ReadOptions`, which defines `totalMemoryLimit?: number` (`src/psd.ts:1819`). A default of 2 GB is written into the reader at `src/psdReader.ts:237`. When the parser reaches a layer, it calls…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-6w3r-6hpr-hp6p

  2. Revision 1 · created ·

    Published from ghsa record GHSA-6w3r-6hpr-hp6p

Agent brief

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

# Patch Next advisory brief: CVE-2026-63501

Advisory: ag-psd: Uncontrolled Memory Allocation in PSD Layer Decoding (totalMemoryLimit bypass)
IDs: CVE-2026-63501, GHSA-6w3r-6hpr-hp6p
Record: https://patchnext.com/advisories/cve-2026-63501 (revision 2, source checked 10 Nov 2026, 06:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ag-psd 31.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm ag-psd: affected < 31.0.1; fixed in 31.0.1

## Suggested inspection (read-only)
- `npm ls ag-psd --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 ag-psd.
- 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://github.com/advisories/GHSA-6w3r-6hpr-hp6p (GitHub-reviewed advisory GHSA-6w3r-6hpr-hp6p lists affected ranges: npm ag-psd >=0 <=31.0.0)
- Verified: https://osv.dev/vulnerability/GHSA-6w3r-6hpr-hp6p (OSV record GHSA-6w3r-6hpr-hp6p lists affected ranges: npm ag-psd >=0 <31.0.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…