# CVE-2026-82380: Apache Roller: CSRF protection bypass via self-generated salt validation

> Remote attackers can trick logged-in users into performing unauthorized actions due to flawed CSRF token validation in Apache Roller.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-33v7-638r-hch5

## What is CVE-2026-82380?

CVE-2026-82380 is a high-severity vulnerability in Apache Roller, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-Site Request Forgery (CSRF) in Apache Roller 6.1.5 allows a remote attacker to cause a logged-in user to perform state-changing actions under the victim's authority, because the CSRF validation filters accept a request that does not submit the required salt token, validating instead against a value the server itself generated for the request. No optional feature or non-default configuration is required; any logged-in author or administrator is affected when induced to visit a crafted page. Users are recommended to upgrade to Apache Roller 6.1.6 or later, which validates only the submitted salt and applies the same check to multipart forms.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-82380 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82380 is a high-severity vulnerability in Apache Roller, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-82380 in the wild and no public exploit code.

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

## Sources

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

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