ag-psd has uncontrolled memory allocation via declared PSD dimensions (DoS)
Impact
ag-psd library versions before 31.0.0 have uncontrolled memory allocation via declared PSD dimensions, allowing attackers to cause a denial of service. Attackers can declare enormous geometry in a tiny PSD file, forcing multi-gigabyte memory allocation. This affects services reading untrusted PSDs.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Version 31.0.0 adds a composite-image allocation limit, but complete coverage of the separately described layer-rectangle allocation path is not established and requires curator residual/scope review.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
Agamnentzar · GitHub_M
ag-psd
1 range
Agamnentzar · GitHub_M
ag-psd
Compare with this publisher’s ranges. This does not inspect your installation.
affected
< 31.0.0
Other versions: unknown
Original source description
ag-psd is a JavaScript library for reading and writing Photoshop Document files. Before the allocation-limit remediation attempt in version 31.0.0, readPsd() commits image and layer buffers from attacker-declared PSD geometry before validating the declarations against the actual available data or sane allocation limits. The psdReader.js implementation sizes off-heap typed arrays using width, height, channels, depth and per-layer rectangles, so a tiny PSD declaring enormous geometry can force multi-gigabyte memory allocation before a later bounds error. The reported 52-byte input on Node 24 produced approximately 3.17 GB peak RSS before a RangeError; under memory pressure the process can be terminated before the error can be caught, and concurrent inputs can exhaust memory. Services reading untrusted PSDs are exposed to denial of service. This differs from genuinely large PSD files whose memory demand is proportional to real input content. Version 31.0.0 adds a composite-image allocation limit, but complete coverage of the separately described layer-rectangle allocation path is not established and requires curator residual/scope review.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-62297View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.