# CVE-2026-46346: Goobi viewer: Predictable Password Reset Token Allows Unauthorized Password Reset


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-gj5g-4rxf-8rmq

## What is CVE-2026-46346?

CVE-2026-46346 is a medium-severity vulnerability in intranda goobi-viewer-core, published on 23 Oct 2026. 

### Official description

The Goobi viewer is a web application that allows digitised material to be displayed in a web browser. Prior to version 26.05, the password reset token is predictably based on the time of the reset request. An attacker who knows the target's email address can request a reset and then brute-force the token. Exploiting this finding alone forces an unauthorized password reset on any account. This issue has been patched in version 26.05.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password), CWE-340 (Generation of Predictable Numbers or Identifiers), CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2026-46346?


## How do I fix CVE-2026-46346?

No fix has been published for CVE-2026-46346 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-46346 being exploited?

There is no known exploitation of CVE-2026-46346 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46346 and fix it if it is affected.

What it is: CVE-2026-46346 is a medium-severity vulnerability in intranda goobi-viewer-core, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-46346 in the wild and no public exploit code.

Affected product: intranda goobi-viewer-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46346/ (Markdown: https://insights.sbomify.com/CVE-2026-46346/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46346
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46346
- OSV: https://osv.dev/vulnerability/CVE-2026-46346

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46346/
Summaries are generated and may contain mistakes; the official description above is the record.