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-113671 Overview
CVE-2026-113671 is a Server-Side Request Forgery (SSRF) vulnerability [CWE-918] in the ApostropheCMS AI helper module. ApostropheCMS is an open-source Node.js content management system. The flaw affects AI helper versions 1.0.0-beta.10 through 1.0.0-beta.12. An authenticated editor with image-generation capability can create a base64-generated image record that lacks a stored provider URL. When image acceptance is invoked on a deployment using local relative storage without a trusted global base URL, the server resolves the uploads path against a request-controlled Host header. This enables bounded server-side requests to an attacker-selected host, port, and HTTP origin.
Critical Impact
Authenticated editors can coerce the ApostropheCMS server into making bounded outbound HTTP requests to attacker-chosen hosts and ports, exposing internal services on affected deployments.
Affected Products
- ApostropheCMS AI helper 1.0.0-beta.10
- ApostropheCMS AI helper 1.0.0-beta.11
- ApostropheCMS AI helper 1.0.0-beta.12
Discovery Timeline
- 2026-10-20 - CVE-2026-113671 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-113671
Vulnerability Analysis
The vulnerability resides in the AI helper image acceptance flow of the @apostrophecms/ai-helper-image module. When an editor generates an image via base64 and no stored provider URL is persisted on the record, the acceptance path reconstructs the asset URL by combining the fixed uploads path with an origin derived from the inbound request. Because that origin is taken from the Host header, an authenticated editor can direct the server to issue an HTTP fetch to a host, port, and scheme of their choice. Scope is bounded: the attacker cannot specify arbitrary paths, and deployments using absolute storage or a stored-provider configuration are not affected.
Root Cause
The root cause is improper trust in request-controlled input when resolving a server-initiated URL [CWE-918]. The acceptance handler lacks a trusted global base URL for local-relative storage and falls back to a Host-derived origin. Combined with records that omit a provider URL, this allows the fetch target to be influenced by the client.
Attack Vector
Exploitation requires an authenticated account with image-generation capability. The attacker generates a base64 image, then submits an acceptance request while supplying a crafted Host header pointing at an internal service or attacker-controlled endpoint. The server performs a bounded outbound HTTP request against that origin at the fixed uploads path, enabling reconnaissance of internal network services reachable from the application host.
See the GitHub Security Advisory GHSA-527g-ff96-x6wj for additional technical context.
// 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 Fix
Detection Methods for CVE-2026-113671
Indicators of Compromise
- Outbound HTTP requests from the ApostropheCMS server to internal RFC1918 addresses or non-standard ports immediately after image acceptance actions.
- Access logs showing image-acceptance requests with Host headers that do not match the deployment's canonical hostname.
- Image records created via base64 generation that lack a stored provider URL field.
Detection Strategies
- Correlate editor-initiated image acceptance events with outbound socket activity from the Node.js process to identify unexpected destinations.
- Alert on HTTP requests originating from the application server that target loopback, link-local, or metadata service addresses such as 169.254.169.254.
- Review authentication logs for editor accounts exercising image-generation capability at unusual rates.
Monitoring Recommendations
- Enable egress logging on the application host and forward it to a centralized analytics platform for retrospective hunting.
- Monitor the AI helper module version in deployed environments and flag any instance still running 1.0.0-beta.10 through 1.0.0-beta.12.
- Instrument the reverse proxy to log the raw Host header on acceptance endpoints for post-incident review.
How to Mitigate CVE-2026-113671
Immediate Actions Required
- Upgrade the @apostrophecms/ai-helper package to 1.0.0-beta.13 or later across all environments.
- Audit editor accounts and revoke image-generation capability from users who do not require it.
- Configure a trusted global base URL for deployments using local relative storage so request-derived origins are not consulted.
Patch Information
The issue is fixed in AI helper 1.0.0-beta.13. Refer to the ApostropheCMS AI Helper Release, the ApostropheCMS Commit Fix, and the ApostropheCMS Commit Update for the applied changes.
Workarounds
- Switch affected deployments to a stored-provider or absolute-storage configuration, which is not impacted by this flaw.
- Enforce strict Host header validation at the reverse proxy or load balancer to reject requests whose Host does not match the deployment's canonical hostname.
- Restrict outbound network egress from the application host to only the destinations required for normal operation.
# Upgrade to the patched AI helper release
npm install @apostrophecms/ai-helper@1.0.0-beta.13
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

