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

published 2026-10-23 16 d ago modified 2026-10-29 10 d ago also EUVD-2026-109065

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 3%
public exploits: 0; none known

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.

Patch / fix

links 2

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 10 d ago (2026-10-29)

Exploit prediction

0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected products

intranda goobi-viewer-core

Classification

Weakness

CWE-306 Missing Authentication for Critical Functionality
CWE-862 Missing Authorization
CWE-1385 Missing Origin Validation in WebSockets

References

Sources

CVE List CVE-2026-55463
NVD CVE-2026-55463

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary