ag-psd can exhaust memory when parsing crafted PSD dimensions

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-62297: 0.34% estimated exploitation activity in the next 30 days; percentile 27.74 (FIRST EPSS, 2026-11-14). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary readPsd() commits the image/layer buffers from the declared header geometry (width x height x channels x depth, and per-layer rectangles) before validating those values against the actual data. A tiny crafted PSD declaring huge geometry forces a multi-gigabyte allocation.

Impact On ag-psd 30.2.0, Node 24, a 52-byte PSD makes readPsd(buf) commit ~3.17 GB (measured peak RSS) in ~0.45 s before throwing a catchable RangeError ("Offset is outside the bounds of the DataView") — about 61,000,000x amplification. Because the buffer is committed before validation, the allocation OOM-kills the process before the error on essentially any host (uncatchable), and concurrent requests exhaust memory. Any service reading untrusted PSDs with ag-psd is exposed to a remote DoS. This is distinct from #39 and #206, which involve genuinely large PSDs (memory proportional to real data). Here the input is 52 bytes: the file declares enormous geometry that is never present, so the allocation…

Published by the source

13 Nov 2026, 23:19 UTC

Last modified by the source

13 Nov 2026, 23:30 UTC

Source last checked

14 Nov 2026, 06:00 UTC

1. Revision 2 · amended · 14 Nov 2026

   Amended from osv record GHSA-qfx6-q44v-9qqw

2. Revision 1 · created · 13 Nov 2026

   Published from ghsa record GHSA-qfx6-q44v-9qqw

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

# Patch Next advisory brief: CVE-2026-62297

Advisory: ag-psd can exhaust memory when parsing crafted PSD dimensions
IDs: CVE-2026-62297, GHSA-qfx6-q44v-9qqw
Record: https://patchnext.com/advisories/cve-2026-62297 (revision 2, source checked 14 Nov 2026, 06:00 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.0. A vendor fix does not mean a deployment is fixed.

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

## 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-qfx6-q44v-9qqw (GitHub-reviewed advisory GHSA-qfx6-q44v-9qqw lists affected ranges: npm ag-psd >=0 <31.0.0)
- Verified: https://osv.dev/vulnerability/GHSA-qfx6-q44v-9qqw (OSV record GHSA-qfx6-q44v-9qqw lists affected ranges: npm ag-psd >=0 <31.0.0 (fixed))

Commands are suggestions: review each one before running it.