dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-45083

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-27
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Goobi viewer is a web application that allows digitised material to be displayed in a web browser. From 4.8.0 to before 26.04.1, the Goobi viewer REST endpoint POST /api/v1/index/stream accepted an arbitrary Solr streaming expression from unauthenticated network clients and forwarded it to the backend Solr server without restriction. An attacker could read the complete Solr index and, in default Solr deployments, also modify or delete indexed records. This vulnerability is fixed in 26.04.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Goobi viewer web application contains a critical unauthenticated injection vulnerability in the REST endpoint POST /api/v1/index/stream. From version 4.8.0 through 26.04.0, this endpoint accepts arbitrary Solr streaming expressions from unauthenticated network clients and forwards them directly to the backend Solr server without any authentication, sanitization, or access controls, enabling complete index read/write/delete operations.

MitigationUpgrade to Goobi viewer version 26.04.1 or later to apply the security patch. As a defense-in-depth measure, implement network-level restrictions to limit which systems can directly access the Solr backend.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Goobi viewer installation and version
    Locate the Goobi viewer web application installation and check the version file or configuration. Common locations include the war file, config files, or the application's main page. Look for version strings such as '4.8.x' through '26.04.x'.
    Affected if The installed version falls within the range 4.8.0 to 26.04.0 inclusive.
  2. Verify the REST API endpoint is exposed
    Confirm that the endpoint POST /api/v1/index/stream is accessible on the Goobi viewer server. This can be done by checking the application's exposed URLs or attempting a test request to the endpoint (ensure you have authorization).
    Affected if The endpoint /api/v1/index/stream is reachable from the network without authentication.
  3. Check Solr backend accessibility
    Identify the Solr server configured for the Goobi viewer and verify whether it accepts connections from the Goobi viewer server or potentially from unauthenticated network clients. Review network configurations and firewall rules.
    Affected if The Solr backend is accessible without proper authentication or network restrictions.
  4. Compare installed version against affected range
    Using the version identified in step 1, compare it to the affected range: versions 4.8.0 through 26.04.0 are vulnerable. Versions below 4.8.0 or above 26.04.0 are not affected by this specific CVE.
    Affected if The installed version is 4.8.0, 26.04.0, or any version in between.

The environment is affected if the Goobi viewer version is between 4.8.0 and 26.04.0 inclusive AND the /api/v1/index/stream endpoint is exposed without additional authentication controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Goobi viewer version 26.04.1 or later to apply the security patch. As a defense-in-depth measure, implement network-level restrictions to limit which systems can directly access the Solr backend.

Recommended fix High confidence

26.04.1

  1. Identify the current Goobi viewer version by checking the deployment or configuration files
  2. If the current version is between 4.8.0 and 26.04.0 (inclusive), plan an upgrade to version 26.04.1 or later
  3. Download the Goobi viewer version 26.04.1 from the official releases or GitHub repository
  4. Follow the standard Goobi viewer upgrade documentation for your deployment method (WAR file, Docker, etc.)
  5. After upgrade, verify that the /api/v1/index/stream endpoint now requires authentication
  6. Test that legitimate authenticated API calls to Solr streaming expressions still function correctly
Caveat The fix adds authentication to the previously unauthenticated endpoint; any automated systems or scripts using this API will need to be updated to provide valid credentials

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45083 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45083 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data