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-113665 Overview
CVE-2026-113665 is a broken access control vulnerability in ApostropheCMS, an open-source Node.js content management system. The notification module exposes PATCH and DELETE REST endpoints that operate directly on the underlying MongoDB collection. These endpoints do not verify that the requester is authenticated or that the requester owns the target notification. An unauthenticated attacker who obtains a valid notification ID can modify or permanently delete another user's notification. The issue is classified as [CWE-639] (Authorization Bypass Through User-Controlled Key) and is fixed in ApostropheCMS version 4.33.0.
Critical Impact
Unauthenticated attackers with a valid notification ID can tamper with or delete notifications belonging to other users, undermining the integrity of in-application alerts.
Affected Products
- ApostropheCMS versions prior to 4.33.0
- ApostropheCMS notification module (@apostrophecms/notification)
- Node.js deployments of ApostropheCMS using the default notification REST API
Discovery Timeline
- 2026-10-20 - CVE-2026-113665 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-113665
Vulnerability Analysis
The ApostropheCMS notification module registers PATCH and DELETE REST routes that interact directly with MongoDB. The handlers perform collection operations keyed on a notification identifier supplied by the client. Access control checks for authentication and ownership are missing from these handlers. As a result, any HTTP client that can reach the endpoint and present a valid notification ID can mutate or remove the matching document. The underlying weakness is [CWE-639], where authorization decisions rely on a user-controlled key without validating the caller's rights to that key.
Root Cause
The notification REST endpoints trust the inbound request to supply a legitimate _id and do not reconcile that identifier against the session user. There is no middleware enforcing that the request originates from an authenticated session, and no check that the notification's owner matches the requesting user. This design allows arbitrary identifier substitution.
Attack Vector
Exploitation requires network access to the ApostropheCMS instance and knowledge of a target notification ID. An attacker who obtains or guesses an ID can issue a DELETE or PATCH request to the notification endpoint and have it processed against the MongoDB collection. The CVSS vector reflects high attack complexity because ID discovery is non-trivial, but once obtained, no authentication is required.
// Patch excerpt from packages/ai-helper/modules/@apostrophecms/ai-helper-image/index.js
methods(self) {
return {
scheduleCleanup() {
- setInterval(self.cleanup, 1000 * 60 * 60);
+ self.cleanupInterval = setInterval(self.cleanup, 1000 * 60 * 60);
},
async cleanup() {
Source: ApostropheCMS Commit f84fd41
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-113665
Indicators of Compromise
- Unauthenticated PATCH or DELETE requests to notification REST routes under /api/v1/@apostrophecms/notification/.
- Server access logs showing successful 2xx responses on notification endpoints without a corresponding authenticated session cookie or bearer token.
- Unexpected removal or modification of user notification documents in the MongoDB aposNotifications collection.
Detection Strategies
- Review web server and reverse proxy logs for PATCH and DELETE requests to notification endpoints originating from unauthenticated clients.
- Enable MongoDB audit logging and watch for notification collection write operations that do not correlate with a logged-in user session.
- Add application-layer logging around notification handlers to record the authenticated user ID alongside each mutation.
Monitoring Recommendations
- Alert on spikes in DELETE traffic to notification routes relative to historical baselines.
- Monitor for enumeration patterns such as sequential or high-volume requests to notification IDs.
- Track response size and status code anomalies on the notification API to detect brute-force ID discovery.
How to Mitigate CVE-2026-113665
Immediate Actions Required
- Upgrade ApostropheCMS to version 4.33.0 or later across all environments.
- Audit MongoDB notification collections for unexpected deletions or modifications since deployment.
- Rotate any API tokens or session secrets if evidence of enumeration is found in access logs.
Patch Information
The fix is included in ApostropheCMS 4.33.0. See the ApostropheCMS Release v4.33.0 notes, the ApostropheCMS Security Advisory GHSA-vwwx-px9w-crrc, and the related commits 9500b8b and f84fd41 for the full set of changes.
Workarounds
- Place the ApostropheCMS instance behind an authenticating reverse proxy that blocks unauthenticated PATCH and DELETE requests to notification routes.
- Apply web application firewall (WAF) rules restricting access to /api/v1/@apostrophecms/notification/* to authenticated sessions only.
- Restrict exposure of the ApostropheCMS admin surface to trusted networks until the upgrade is applied.
# Example nginx rule blocking unauthenticated PATCH/DELETE on the notification API
location ~ ^/api/v1/@apostrophecms/notification/ {
limit_except GET POST {
deny all;
}
proxy_pass http://apostrophecms_upstream;
}
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

