CVE-2026-82378: Apache Roller incorrect authorization in OAuth 1.0a endpoint

CVE-2026-82378 · Severity: critical · CVSS 9 · Published 2026-09-28

Apache Roller's OAuth 1.0a login feature contains an authorization bypass that allows an attacker to bind a request token to any user account, including administrator accounts, without proper authentication. An attacker who knows an outstanding request token can hijack login flows to gain unauthorized access to any account on affected Roller installations that have OAuth configured.

Technologies: Apache Roller. Vendors: Apache.

Quick answers

Is CVE-2026-82378 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-82378 being exploited in the wild.
How severe is CVE-2026-82378?
Critical severity, with a CVSS score of 9, published 28 September 2026.
Which products and versions are affected?
Apache Roller 6.1.5 and earlier.
Is there a fix for CVE-2026-82378?
A patch was published on 2026-09-05: Fix merged in PR #165 to version 6.1.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-82378 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-82378?
Check whether you run Apache Roller at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The OAuth 1.0a authorization endpoint incorrectly derives the authorizing user identity from request parameters rather than the authenticated session, allowing an unauthenticated attacker to bind an arbitrary user to a request token. Exploitation requires knowledge of an outstanding request token from a configured site-wide OAuth consumer. The vulnerability is fixed in version 6.1.6 and later by binding authorization to the logged-in session.

Affected products

  • Apache Roller 6.1.5 and earlier

Timeline

  • 2026-09-28: disclosed
  • 2026-09-05: patched: Fix merged in PR #165 to version 6.1.6

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.