External risk intelligence

Goobi Viewer Path Traversal to Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-46652

The vulnerability exists in the Goobi viewer, which is a web application designed to display digitized material to users in a web browser. As a web application that is typically deployed to serve content to end users over the internet, it functions as an externally reachable service, making its web-facing components commonly exposed.

Path Traversal

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability has been identified in the Goobi viewer, a web application used for displaying digitized materials. This issue could allow an attacker to execute code remotely on systems running vulnerable versions of the software. The main concern is to confirm if our organization uses this technology and assess the potential exposure.

  • Goobi viewer can be tricked into writing files anywhere.
  • Remote code execution poses a significant system compromise risk.
  • Confirm usage and assess potential impact.

Attack Path

How an attacker could exploit the issue

An attacker could leverage an unauthenticated network connection to trick the Goobi viewer into downloading a specially crafted file. This file's name, provided by an attacker-controlled server, would contain commands that trick the viewer into writing files to arbitrary locations on the server. If these locations are within the viewer's own deployed directory, this could lead to the attacker gaining control of the server.

  • Attacker controls a malicious server.
  • Viewer downloads a file with a malicious name.
  • Leads to remote code execution.

Live Threat

Current exploitation, exposure, and threat context

The Goobi viewer could allow an attacker to write arbitrary files to the server when it fetches content from a malicious HTTP server. This could lead to remote code execution on the system running the Tomcat process.

  • Deployed web application files.
  • Fetching from a malicious HTTP server.
  • Remote code execution as the Tomcat user.

Operational Fix

Recommended remediation, mitigation, and detection steps

Ownership of this vulnerability likely falls to the teams managing the Goobi viewer application, potentially platform or infrastructure teams, with support from security and vendor management if the viewer is externally sourced. The immediate first step is to identify all instances of the Goobi viewer, confirm their exposure and criticality, and then engage the accountable owners to plan remediation.

  • Identify affected Goobi viewer instances.
  • Verify exposure and business criticality.
  • Plan and execute remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Goobi viewer application?

Goobi viewer is a specialized web-based software platform used by archives, libraries, and museums to present digitized collections online. It functions as a viewer that allows users to interact with and browse historical materials directly in their web browsers. Because it handles various media and external resources, the software includes components designed to fetch and process files from remote locations for display.

What is the weakness behind CVE-2026-46652?

This vulnerability is classified as Path Traversal (CWE-22) and External Control of File Name (CWE-73). It occurs because the software accepts file names directly from an external source without cleaning them. An attacker can include path traversal sequences, like moving up directories, to trick the application into saving a file outside of its intended folder, eventually allowing the attacker to overwrite or create files anywhere the system has permission.

How does an attacker trigger this vulnerability?

The trigger requires the Goobi viewer to fetch a file from an attacker-controlled HTTP server. When the viewer processes the response, it blindly uses the file name provided by the malicious server to determine where to store the data locally. This bug is not triggered by normal, legitimate user interactions; it specifically relies on the application being directed to interact with an untrusted, malicious remote server.

Is my Goobi viewer instance at risk?

According to Halo Surface Signal, this software is typically deployed as a web-facing service to make digital collections accessible over the internet. If your instance is reachable from the network, it is considered externally exposed. Systems that are isolated or only accessible within an internal network may face a lower immediate risk, but any instance running vulnerable versions should be treated as a priority for assessment.

What should I do to secure my system?

The primary response is to update your Goobi viewer deployment to version 26.05 or later, which contains the fix for this issue. First, locate all active installations within your environment to understand your footprint. Once identified, prioritize these systems for the software update to ensure the application no longer processes malicious file path instructions from external servers.

References