CVE-2026-46651 Unauthenticated SSRF and local file inclusion via DownloadTaskEndpoint WebSocket in Goobi viewer
Critical 9.8
Published
Updated
Check this codebase for CVE-2026-46651 and fix it if it is affected.
What it is: CVE-2026-46651 is a critical vulnerability in intranda goobi-viewer-core, published on 23 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-46651 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-46651/ (Markdown: https://insights.sbomify.com/CVE-2026-46651/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-46651?
CVE-2026-46651 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, the DownloadTaskEndpoint WebSocket endpoint (/tasks/download/monitor.socket) in goobi-viewer-core accepts download requests from unauthenticated users. This issue has been patched in version 26.05.
Which versions are affected by CVE-2026-46651?
How do I fix CVE-2026-46651?
No fix has been published for CVE-2026-46651 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-46651 being exploited?
There is no known exploitation of CVE-2026-46651 in the wild and no public exploit code.
Sources
Also known as GHSA-79jg-3m2m-jgc8.