# CVE-2026-116897: REDAXO before 5.21.4 Missing Authorization in Version and History Previews


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-f7g4-vhhq-7w9x, GHSA-v4m9-jvvr-83cx

## What is CVE-2026-116897?

CVE-2026-116897 is a high-severity vulnerability in redaxo core, published on 27 Oct 2026. 

### Official description

REDAXO core before 5.21.4 contains a missing authorization vulnerability in the structure/version and structure/history frontend preview modes, which do not check category or clang permissions for the previewed article. Any backend user, or one holding history[article_rollback], can set rex_version or rex_history_date with arbitrary article_id values to read unpublished working versions and historic or deleted content.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-116897 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116897 is a high-severity vulnerability in redaxo core, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116897 in the wild and no public exploit code.

Affected product: redaxo 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-116897/ (Markdown: https://insights.sbomify.com/CVE-2026-116897/index.md)
```

## Sources

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

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