Skip to main content
← All vulnerabilities
CVE-2026-55463EUVD-2026-109065GHSA-H5M9-FPVW-QR36

Goobi viewer: WebSocket endpoints lack server-side authentication and origin validation

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 26.05
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

The Goobi viewer, a web application for displaying digitised material in a browser, is affected, specifically its WebSocket endpoints in the goobi-viewer-core component. An unauthenticated attacker can connect to these endpoints and send forged messages, such as fake page locks that disrupt reviewers' crowdsourcing work.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original description

The Goobi viewer is a web application that allows digitised material to be displayed in a web browser. From version 4.11.0 to before version 26.05, several Jakarta WebSocket endpoints in goobi-viewer-core (DownloadTaskEndpoint, CampaignEndpoint, AutocompleteEndpoint, UserEndpoint) accept connections without verifying that the associated HttpSession belongs to a logged-in user, and none validate the Origin header against an allowlist. An unauthenticated attacker can therefore connect to these endpoints; through CampaignEndpoint this allows polluting the in-process crowdsourcing page-lock map and broadcasting forged lock messages, disrupting reviewers' work. This issue has been patched in version 26.05.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • intranda goobi-viewer-core

    From 4.11.0 · fixed in 26.05

References 3

GitHub · intranda/goobi-viewer-core