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-112069 Overview
CVE-2026-112069 is a missing authorization vulnerability [CWE-862] affecting a TYPO3 extension that enforces access protection on files stored in file storages. The extension failed to apply its access protection when the targeted file storage used a non-default relative base path. Affected files were served directly by the web server without authentication or permission checks. The issue only manifests on websites running TYPO3 14.3.
Critical Impact
Unauthenticated remote attackers can retrieve files that administrators expected to be access-protected, leading to disclosure of restricted documents hosted in TYPO3 file storages with a non-default relative base path.
Affected Products
- TYPO3 CMS 14.3 deployments using the affected access-protection extension
- File storages configured with a non-default relative base path
- Web-exposed TYPO3 instances relying on the extension for file ACLs
Discovery Timeline
- 2026-10-20 - CVE-2026-112069 published to the National Vulnerability Database (NVD)
- 2026-10-20 - TYPO3 publishes TYPO3 Security Advisory #2026-028
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-112069
Vulnerability Analysis
The vulnerability is a missing authorization flaw [CWE-862] in a TYPO3 extension responsible for gating access to files held in TYPO3 file storages. When a storage is configured with the default base path, the extension correctly intercepts requests and evaluates permissions. When the storage is configured with a non-default relative base path, the extension's protection logic does not apply. Requests for files under that storage reach the web server directly and are returned without any authentication or permission evaluation.
The weakness exposes any file placed in such a storage, including documents intended only for authenticated users or members of specific groups. Exploitation requires only a network-reachable TYPO3 14.3 instance that uses the extension in combination with a non-default relative base path. No credentials and no user interaction are required.
Root Cause
The root cause is an incomplete authorization check tied to how the extension resolves the storage base path. The protection routine assumed the default base path layout, so storages configured with a non-default relative base path were omitted from the enforcement scope. As a result, requests to those paths were handled by the underlying web server rather than routed through the TYPO3 permission layer.
Attack Vector
An unauthenticated attacker sends an HTTP request directly to the URL of a file located inside a non-default relative base path storage. Because the web server serves the file without consulting the extension, the attacker receives the file contents regardless of configured access restrictions. Attackers typically discover candidate paths by crawling the site, reading HTML references, or guessing predictable file names. See the TYPO3 Security Advisory #2026-028 for additional technical details.
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-112069
Indicators of Compromise
- Unauthenticated HTTP GET requests to files inside TYPO3 storages that use a non-default relative base path.
- Successful 200 OK responses for file URLs that should have required an authenticated session or group membership.
- Access log entries for restricted file paths without any preceding TYPO3 authentication activity for the same client.
Detection Strategies
- Inventory all TYPO3 14.3 sites and enumerate file storages whose base path is relative and non-default.
- Compare web server access logs against TYPO3 session or login logs to identify file retrievals that bypassed authentication.
- Perform authenticated and unauthenticated test fetches against sample protected files and flag any discrepancies in response codes or content length.
Monitoring Recommendations
- Alert on repeated unauthenticated requests to directories backing TYPO3 file storages.
- Monitor for enumeration patterns such as sequential or dictionary-style requests against storage directories.
- Forward TYPO3 and web server logs to a centralized analytics platform and build correlation rules for file-access anomalies.
How to Mitigate CVE-2026-112069
Immediate Actions Required
- Upgrade the affected TYPO3 extension to the fixed version listed in TYPO3 Security Advisory #2026-028.
- Audit TYPO3 file storages and identify any using a non-default relative base path on TYPO3 14.3 installations.
- Review web server access logs for prior unauthenticated access to files that were intended to be protected.
Patch Information
TYPO3 has published fixed releases of the affected extension in TYPO3 Security Advisory #2026-028. Administrators should install the patched version through Composer or the TYPO3 Extension Manager and verify the extension version after deployment.
Workarounds
- Reconfigure affected file storages to use the default base path so the extension's protection logic applies.
- Restrict direct web server access to storage directories using web server rules such as Deny directives or location blocks that require TYPO3-mediated access.
- Temporarily remove or relocate sensitive files from affected storages until the patched extension version is deployed.
# Example nginx configuration restricting direct access to a TYPO3 file storage directory
location ^~ /fileadmin/protected/ {
deny all;
return 403;
}
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

