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

CVE-2026-107188: File Upload RCE Vulnerability

CVE-2026-107188 is a critical file upload vulnerability that enables remote code execution through malicious JSP files. When chained with authentication bypass, attackers can execute commands without credentials. This article covers technical details, exploitation risks, affected systems, 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-107188 Overview

CVE-2026-107188 is an unrestricted file upload vulnerability [CWE-434] affecting Eptura Archibus. The flaw allows an authenticated user to upload export reports containing arbitrary file contents, including JavaServer Pages (JSP) code, under attacker-controlled extensions such as .jspx. Any user can then browse to the uploaded file, triggering server-side execution. When chained with a separate authentication bypass vulnerability disclosed in the same advisory, unauthenticated attackers can achieve remote code execution on the server.

Critical Impact

Attackers can execute arbitrary code on affected Archibus servers, leading to full compromise of application data and workflows managed by the facility management platform.

Affected Products

  • Eptura Archibus (versions prior to vendor-released fix)
  • Deployments exposing the export report upload functionality
  • Instances reachable over the network by low-privileged users

Discovery Timeline

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

Technical Details for CVE-2026-107188

Vulnerability Analysis

The vulnerability resides in the export report upload handler within Eptura Archibus. The handler accepts user-supplied file content and file extension without validating either value against an allow-list. An attacker can upload a file containing JSP code and assign the .jspx extension, which the servlet container will compile and execute when requested. Because the uploaded file is reachable by any user via a predictable URL path, exploitation requires only a single HTTP request after upload.

The advisory references a chained authentication bypass that eliminates the authentication prerequisite. Combined, these two issues produce an unauthenticated remote code execution path against the server.

Root Cause

The root cause is unrestricted file upload [CWE-434]. The application fails to validate file contents, enforce extension allow-listing, or store uploads outside the web-executable path. Both the file body and the extension are attacker-controlled, which lets arbitrary server-side script content reach a location where the application server will execute it.

Attack Vector

Exploitation is network-based and requires low attack complexity. An attacker with low-privileged credentials, or an unauthenticated attacker leveraging the companion authentication bypass, submits a crafted upload request containing JSP source and a .jspx extension. The attacker then issues a GET request to the uploaded file path. The servlet container compiles and runs the payload under the Archibus application process context, enabling arbitrary command execution.

See the Rapid7 blog on the Eptura Archibus fix for the published technical analysis.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-107188

Indicators of Compromise

  • Files with .jsp, .jspx, or other server-executable extensions written to directories that normally hold export report artifacts.
  • HTTP POST requests to the export report upload endpoint containing JSP tags such as <% or <jsp: in the request body.
  • Subsequent GET requests to uploaded report filenames that return dynamic content or shell command output.
  • Child processes spawned by the Archibus application server such as cmd.exe, powershell.exe, /bin/sh, or bash.

Detection Strategies

  • Inspect web server and application logs for upload requests followed by direct retrieval of files with scripting extensions.
  • Monitor the Archibus upload directory for new files whose extensions fall outside the expected report format set (for example, .xlsx, .pdf, .csv).
  • Correlate unauthenticated session activity with POSTs to upload endpoints to surface authentication bypass chaining.

Monitoring Recommendations

  • Enable file integrity monitoring on web-accessible directories used by Archibus.
  • Forward application and servlet container logs to a centralized analytics platform for retention and correlation.
  • Alert on process-execution telemetry showing shell or scripting interpreters spawned by the Java application server user.

How to Mitigate CVE-2026-107188

Immediate Actions Required

  • Apply the vendor-released Archibus update that addresses the file upload and authentication bypass vulnerabilities referenced in the Rapid7 advisory.
  • Restrict network access to the Archibus application to trusted users and management networks until patched.
  • Audit the upload directory for unexpected files with executable extensions and remove any suspicious artifacts.
  • Rotate credentials and session tokens for any account that may have interacted with the exposed instance.

Patch Information

Eptura has released a fix for the chained vulnerabilities in Archibus. Administrators should consult the vendor advisory and the Rapid7 writeup for the specific fixed version and apply it across all production and non-production instances.

Workarounds

  • Block upload requests to the export report endpoint at a reverse proxy or web application firewall where feasible.
  • Configure the servlet container to deny execution of JSP files located in user-writable directories.
  • Enforce strict extension and MIME type allow-listing at an upstream filtering layer for all file uploads.
bash
# Example WAF rule concept to block JSP content in uploads
# Reject POST bodies containing JSP tags targeting the Archibus upload path
SecRule REQUEST_URI "@contains /archibus/" \
  "chain,id:1072026,phase:2,deny,status:403,msg:'Blocked JSP upload to Archibus'"
  SecRule REQUEST_BODY "@rx (<%|<jsp:|<%@)" "t:none"

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.