# CVE-2026-92120: Apache Allura: Oauth1 Replay Attack


- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-ccrf-jfj2-x65f

## What is CVE-2026-92120?

CVE-2026-92120 is a critical vulnerability in Apache Allura, published on 12 Oct 2026. 

### Official description

OAuth1 Request Replay Attack vulnerability in Apache Allura.

This issue affects Apache Allura: through 1.21.0.

Users are recommended to upgrade to version 1.22.0 which fixes the issue.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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


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

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

## Is CVE-2026-92120 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92120 is a critical vulnerability in Apache Allura, published on 12 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92120 in the wild and no public exploit code.

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

## Sources

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

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