Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-82378 – Authentication Bypass via OAuth Token Hijacking – Apache Roller 6.1.5

Be the first to know when new zero-days emerge:

Summary

CVE-2026-82378 is an Incorrect Authorization vulnerability in the OAuth 1.0a authorization endpoint of Apache Roller. An unauthenticated remote attacker who learns an outstanding OAuth request token can bind that token to an arbitrary user account — including an administrator account — by submitting an unsigned authorization request. The flaw carries a Critical CVSS score of 9.0 and affects Apache Roller 6.1.5.

Technical details

  • Root cause: The OAuth 1.0a authorization endpoint derives the identity of the user granting authorization from a request-supplied parameter rather than validating it against the authenticated session.
  • Trigger conditions: The target installation must have a site-wide OAuth 1.0a consumer configured, and the attacker must know (or otherwise obtain) an outstanding request token issued by that consumer flow.
  • Attack vector: Network-based; the attacker submits an unsigned authorization request referencing the known request token, without needing valid credentials.
  • Impact: Successful exploitation lets an attacker bind the OAuth token to any account, including an administrator, enabling subsequent access as that user via the OAuth-authenticated API — resulting in full compromise of confidentiality, integrity, and availability of the affected Roller instance.

Affected software

  • Apache Roller 6.1.5 (and prior versions using the same OAuth 1.0a authorization flow), where a site-wide OAuth 1.0a consumer is configured
  • Fixed in Apache Roller 6.1.6

Severity

  • CVSS v3.1 Base Score: 9.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to Apache Roller 6.1.6 or later, which binds OAuth authorization decisions to the authenticated session rather than a request-supplied identity value.
  • If unable to patch immediately: Disable or remove any configured site-wide OAuth 1.0a consumer until the upgrade can be applied, and restrict access to administrative and management interfaces to trusted networks.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge