# CVE-2026-46652: The Goobi viewer is a web application that allows digitised material to be displayed in a web browser.


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-r386-2frm-w3v6

## What is CVE-2026-46652?

CVE-2026-46652 is a critical vulnerability in intranda goobi-viewer-core, published on 23 Oct 2026. 

### Official description

The Goobi viewer is a web application that allows digitised material to be displayed in a web browser. From version 24.03 to before version 26.05, ExternalFilesDownloader.getFilename() extracts the destination filename from a server-supplied Content-Disposition response header and passes it directly to Path.resolve() without stripping directory components. This allows for a malicious HTTP server that the viewer fetches from to supply an absolute path or ../ traversal sequences as the filename, writing attacker-controlled content to an arbitrary path writable by the Tomcat process. When targeting the deployed web-application directory, this yields remote code execution as the tomcat OS user. This issue has been patched in version 26.05.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-46652?


## How do I fix CVE-2026-46652?

No fix has been published for CVE-2026-46652 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-46652 being exploited?

There is no known exploitation of CVE-2026-46652 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46652 and fix it if it is affected.

What it is: CVE-2026-46652 is a critical vulnerability in intranda goobi-viewer-core, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-46652 in the wild and no public exploit code.

Affected product: intranda goobi-viewer-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46652/ (Markdown: https://insights.sbomify.com/CVE-2026-46652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46652
- OSV: https://osv.dev/vulnerability/CVE-2026-46652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46652/
Summaries are generated and may contain mistakes; the official description above is the record.