Quick answers
- Is CVE-2026-55457 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55457 being exploited in the wild.
- How severe is CVE-2026-55457?
- High severity, with a CVSS score of 7.4, published 23 October 2026.
- Which products and versions are affected?
- Intranda Goobi viewer before 26.05.
- Is there a fix for CVE-2026-55457?
- Yes: fixed in 26.05. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55457 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-55457?
- Check whether you run Intranda Goobi viewer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 26.05
Technical details
The AuthorizationFilter compares supplied tokens against a default empty string returned by Configuration.getWebApiToken() when webapi.authorization.token is not configured, without first validating that a token is actually set. This allows network-based attackers to access @AuthorizationBinding-protected REST endpoints by sending requests with an empty or missing ?token= parameter. The vulnerability affects the REST API authorization mechanism prior to version 26.05.
Affected products
- intranda Goobi viewer before 26.05
Timeline
- 2026-10-23: disclosed