Categories
CVE-2026-45083 critical CVSS 9.8

Vulnerability in io.goobi.viewer:viewer-core (CVE-2026-45083)

Summary

Vulnerability in io.goobi.viewer:viewer-core (CVE-2026-45083). Successful exploitation can lead to full system takeover. Exploitable via POST /api/v1/index/stream.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-45083 has been found in io.goobi.viewer:viewer-core.
Attackers can target a specific entry point like POST /api/v1/index/stream over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "io.goobi.viewer:viewer-core CVE-2026-45083" on the vendor's site.

CVE-2026-45083 (io.goobi.viewer:viewer-core) — CWE-306 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/v1/index/stream / ACCESSCONDITION
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-306) exists in io.goobi.viewer:viewer-core. Attackers reach the vulnerable code path via POST /api/v1/index/stream without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of io.goobi.viewer:viewer-core. Attack surface: POST /api/v1/index/stream / ACCESSCONDITION.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/v1/index/stream requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで io.goobi.viewer:viewer-core を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect
    grep 'POST /api/v1/index/stream' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/v1/index/stream への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify
    Replay attack against POST /api/v1/index/stream on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven io.goobi.viewer:viewer-core
[{"type":"ECOSYSTEM","events":[{"introduced":"4.8.0"},{"last_affected":"26.04"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details