ApostropheCMS: Arbitrary file read via import-export attachment-name path traversal
CVE-2026-63667GHSA-79qf-vqgc-7xx3
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@apostrophecms/import-export 3.6.2), 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.
Affected packages
npm @apostrophecms/import-export
- Affected
- < 3.6.2
- Fixed in
- 3.6.2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-79qf-vqgc-7xx3 lists affected ranges: npm @apostrophecms/import-export >=0 <=3.6.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-79qf-vqgc-7xx3 lists affected ranges: npm @apostrophecms/import-export >=0 <3.6.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-63667: 0.46% estimated exploitation activity in the next 30 days; percentile 40.31 (FIRST EPSS, 2026-11-03). 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 `@apostrophecms/import-export` module reconstructs the on-disk source path of every imported attachment from JSON metadata contained in the uploaded archive. The archive carries an `aposAttachments.json` file whose `name` and `extension` fields are concatenated into a filesystem path with no traversal check. The zip-slip guard that the module applies during tar extraction validates tar entry names only and does not cover this second path, which is built after extraction. The file at the resulting path is read and copied into the public uploads directory, then served over HTTP without authentication. A `../` sequence in `name` makes the module read a file outside the extraction directory and publish it at an anonymous URL. Result: an authenticated contributor reads any file on the host whose name ends in an allowlisted extension (other users' uploaded documents, text or CSV dumps, PDFs) by importing a crafted archive and fetching the planted attachment anonymously. ##…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from osv record GHSA-79qf-vqgc-7xx3
- Revision 2 · amended ·
Amended from ghsa record GHSA-79qf-vqgc-7xx3
- Revision 1 · created ·
Published from ghsa record GHSA-79qf-vqgc-7xx3
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-63667 Advisory: ApostropheCMS: Arbitrary file read via import-export attachment-name path traversal IDs: CVE-2026-63667, GHSA-79qf-vqgc-7xx3 Record: https://patchnext.com/advisories/cve-2026-63667 (revision 3, source checked 3 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: Medium (CVSS 6.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @apostrophecms/import-export 3.6.2. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @apostrophecms/import-export: affected < 3.6.2; fixed in 3.6.2 ## Suggested inspection (read-only) - `npm ls @apostrophecms/import-export --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 @apostrophecms/import-export. - 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-79qf-vqgc-7xx3 (GitHub-reviewed advisory GHSA-79qf-vqgc-7xx3 lists affected ranges: npm @apostrophecms/import-export >=0 <=3.6.1) - Verified: https://osv.dev/vulnerability/GHSA-79qf-vqgc-7xx3 (OSV record GHSA-79qf-vqgc-7xx3 lists affected ranges: npm @apostrophecms/import-export >=0 <3.6.2 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…