ApostropheCMS import-export: NoSQL injection via update-key value lets a crafted import match and overwrite an unidentified document
CVE-2026-113662GHSA-jqw5-w6h3-44g6
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@apostrophecms/import-export 3.7.0), 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.7.0
- Fixed in
- 3.7.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-jqw5-w6h3-44g6 lists affected ranges: npm @apostrophecms/import-export >=0 <3.7.0
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-jqw5-w6h3-44g6 lists affected ranges: npm @apostrophecms/import-export >=0 <3.7.0 (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
- 5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- EPSS
- CVE-2026-113662: 0.30% estimated exploitation activity in the next 30 days; percentile 22.85 (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 @apostrophecms/import-export's update-by-key feature lets an imported document carry a <field:key property (for example slug:key) whose value is used to find an existing document to update instead of inserting a new one. getUpdateKey()/insertOrUpdateDocWithKey() (lib/methods/import.js) use that value directly as a MongoDB query value with no laundering: Archive documents are parsed with EJSON (see lib/formats/gzip.js), which revives objects such as { $ne: null } as live values, the same untrusted data source and revival mechanism already fixed once in this module for findSingletonAposDocId/findParkedAposDocId in GHSA-79qf-vqgc-7xx3. That fix did not touch insertOrUpdateDocWithKey, so the identical class of bug survives here: a crafted "slug:key": { "$ne": null } entry in an archive's aposDocs.json makes the import match (and then update) an existing document the archive's author never actually identified, instead of failing to find a match. Impact Reaching this requires only…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-jqw5-w6h3-44g6
- Revision 2 · amended ·
Amended from osv record GHSA-jqw5-w6h3-44g6
- Revision 1 · created ·
Published from ghsa record GHSA-jqw5-w6h3-44g6
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-113662 Advisory: ApostropheCMS import-export: NoSQL injection via update-key value lets a crafted import match and overwrite an unidentified document IDs: CVE-2026-113662, GHSA-jqw5-w6h3-44g6 Record: https://patchnext.com/advisories/cve-2026-113662 (revision 3, source checked 26 Oct 2026, 13:07 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.4) 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.7.0. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @apostrophecms/import-export: affected < 3.7.0; fixed in 3.7.0 ## 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-jqw5-w6h3-44g6 (GitHub-reviewed advisory GHSA-jqw5-w6h3-44g6 lists affected ranges: npm @apostrophecms/import-export >=0 <3.7.0) - Verified: https://osv.dev/vulnerability/GHSA-jqw5-w6h3-44g6 (OSV record GHSA-jqw5-w6h3-44g6 lists affected ranges: npm @apostrophecms/import-export >=0 <3.7.0 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…