Skip to main content
Vulnerability Database/CVE-2026-113666

CVE-2026-113666: ApostropheCMS Denial of Service Vulnerability

CVE-2026-113666 is a denial of service vulnerability in ApostropheCMS that allows authenticated users to cause process-wide availability issues. This article covers the technical details, affected versions, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-113666 Overview

ApostropheCMS is an open-source Node.js content management system. A vulnerability in the db-connect package allows accounts with view-draft access to submit a projection exclusion path that traverses the constructor prototype chain to a shared prototype member. When the application uses a SQLite, PostgreSQL, or multipostgres adapter and has a matching document, the unsetNestedField helper deletes the shared runtime member. This produces persistent, process-wide integrity and availability effects. Every editing role has view-draft access, and guestApiAccess broadens the prerequisite to any logged-in account. The default MongoDB adapter is not affected. The issue is fixed in db-connect 1.1.0 and ApostropheCMS 4.33.0.

Critical Impact

An authenticated user with view-draft access can corrupt shared runtime state across the entire ApostropheCMS process, resulting in persistent denial of service against any installation using SQLite, PostgreSQL, or multipostgres adapters.

Affected Products

  • ApostropheCMS versions prior to 4.33.0
  • @apostrophecms/db-connect versions prior to 1.1.0
  • Deployments using SQLite, PostgreSQL, or multipostgres adapters

Discovery Timeline

  • 2026-10-20 - CVE-2026-113666 published to NVD
  • 2026-10-20 - Last updated in NVD database

Technical Details for CVE-2026-113666

Vulnerability Analysis

The vulnerability is a prototype pollution flaw classified under [CWE-400] (Uncontrolled Resource Consumption). An authenticated user submits a crafted projection exclusion path through the API. The path contains property segments that traverse the JavaScript constructor prototype chain. When the SQLite, PostgreSQL, or multipostgres adapter processes a matching document, the server resolves the path to a shared prototype member instead of a document field.

The unsetNestedField helper then deletes that shared member. Because prototype members are shared across all instances in the Node.js process, the deletion persists for the lifetime of the process. Subsequent requests that depend on the removed prototype member fail, producing persistent integrity and availability impact without requiring a restart to trigger and without recovery short of a restart. The MongoDB adapter is unaffected because its projection handling does not invoke the vulnerable helper path.

Root Cause

The root cause is missing validation of projection exclusion path segments. The unsetNestedField helper walks user-supplied path segments and operates on the resolved target without checking whether traversal has crossed the prototype boundary via constructor, prototype, or __proto__. Combined with view-draft access being granted to every editing role, the attack surface is broad.

Attack Vector

The attack is network-reachable and requires low privileges. Any logged-in account with view-draft permission, or any authenticated user when guestApiAccess is enabled, can submit the malicious projection. The exploitation flow:

  1. Authenticate to the ApostropheCMS instance.
  2. Issue an API request that queries a document type backed by the affected adapter.
  3. Supply a projection exclusion path whose segments traverse constructor.prototype to a shared runtime member.
  4. The server executes unsetNestedField, removing the member from the shared prototype.
  5. The process-wide corruption breaks dependent code paths until restart.

Reference the ApostropheCMS Security Advisory GHSA-j5rq-xfvr-p969 for additional details.

Detection Methods for CVE-2026-113666

Indicators of Compromise

  • API requests containing projection parameters with segments such as constructor, prototype, or __proto__ in exclusion paths.
  • Unexplained server-side errors or undefined is not a function exceptions appearing after a specific authenticated request, persisting until process restart.
  • Repeated 5xx responses on endpoints that were previously stable, correlated with recent view-draft API activity.

Detection Strategies

  • Inspect ApostropheCMS access logs for API calls where projection fields include prototype chain tokens.
  • Correlate the first appearance of recurring runtime errors with the timestamp and session of the request that preceded them.
  • Audit role assignments for accounts holding view-draft access and verify whether guestApiAccess is enabled.

Monitoring Recommendations

  • Enable verbose request logging on ApostropheCMS API endpoints, retaining the full query string and request body.
  • Alert on process crashes and sustained error-rate spikes on Node.js worker processes serving ApostropheCMS.
  • Monitor npm dependency manifests to confirm @apostrophecms/db-connect is at 1.1.0 or later and apostrophe is at 4.33.0 or later.

How to Mitigate CVE-2026-113666

Immediate Actions Required

  • Upgrade @apostrophecms/db-connect to 1.1.0 and apostrophe to 4.33.0.
  • If immediate upgrade is not possible, disable guestApiAccess to limit the attack surface to accounts with editing roles.
  • Review and reduce the set of accounts granted view-draft access until patching is complete.

Patch Information

The fix ships in ApostropheCMS Release 4.33.0 and ApostropheCMS DB Connect Release 1.1.0. Relevant commits are commit 9500b8b and commit f84fd41c.

Workarounds

  • Switch to the default MongoDB adapter, which is not affected by this vulnerability.
  • Place a reverse-proxy filter in front of ApostropheCMS that rejects API requests whose projection parameters contain constructor, prototype, or __proto__ segments.
  • Restart affected Node.js processes to clear in-memory prototype corruption after any suspected exploitation.
bash
# Upgrade ApostropheCMS and db-connect to patched versions
npm install apostrophe@^4.33.0 @apostrophecms/db-connect@^1.1.0

# Verify installed versions
npm ls apostrophe @apostrophecms/db-connect

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.