# CVE-2026-118196: Apache Allura OAuth 1 rebinding vulnerability

Source: https://junglewise.ai/threats/cve-2026-118196-oauth-1-rebinding-vulnerability-in-apache-allura-this-issue  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-09. Updated: 2026-11-09  
License: CC BY 4.0 with a link back

CVE-2026-118196 · Severity: info · Published 2026-11-09

Apache Allura, a collaborative development platform, contains an OAuth 1 rebinding vulnerability that could allow attackers to hijack user authentication tokens and impersonate legitimate users. This vulnerability affects all versions through 1.22.0 and is fixed in version 1.22.1. Users should upgrade immediately to prevent account takeover and unauthorized access to project data.

Technologies: [Apache Allura](https://junglewise.ai/threats/technologies/allura). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-118196 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-118196 being exploited in the wild.

**How severe is CVE-2026-118196?** Informational severity, published 9 November 2026.

**Which products and versions are affected?** Apache Allura through 1.22.0.

**Is there a fix for CVE-2026-118196?** Yes: fixed in 1.22.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-118196 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-118196?** Check whether you run Apache Allura 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.

## How to fix

- Fixed in 1.22.1

## Technical details

The vulnerability is an OAuth 1 rebinding attack in Apache Allura's authentication mechanism. OAuth 1 tokens through version 1.22.0 can be rebound to different applications or contexts, allowing an attacker with access to a token to use it for unintended purposes or to impersonate users across different services. This is resolved in version 1.22.1.

## Affected products

- Apache Allura through 1.22.0

## Timeline

- 2026-11-06: disclosed
- 2026-11-09: patched

## References

- [https://lists.apache.org/thread.html/2x7c9741d50xw3o10h92rk19cr55trof](https://lists.apache.org/thread.html/2x7c9741d50xw3o10h92rk19cr55trof)
- [http://www.openwall.com/lists/oss-security/2026/11/07/1](http://www.openwall.com/lists/oss-security/2026/11/07/1)

## Related threats

- [Apache Allura OAuth1 request replay attack](https://junglewise.ai/threats/cve-2026-92120-oauth1-request-replay-attack-vulnerability-in-apache-allura-this)
- [Apache Allura REST API mass assignment vulnerability](https://junglewise.ai/threats/cve-2026-92119-rest-api-mass-assignment-vulnerability-in-apache-allura-this)
- [Apache Allura OAuth1 callback validation vulnerability](https://junglewise.ai/threats/cve-2026-92116-oauth1-callback-validation-vulnerability-in-apache-allura-this)
- [Apache Allura stored XSS in SVN repositories](https://junglewise.ai/threats/cve-2026-80190-apache-allura-stored-xss-in-svn-repositories)
- [Apache Allura exposure of non-public information via search](https://junglewise.ai/threats/cve-2026-81270-apache-allura-exposure-of-non-public-information-via-search)