CVE-2026-73238: Apache Allura XSS in code display

CVE-2026-73238 · Severity: medium · CVSS 6.1 · Published 2026-08-12

Apache Allura is an open-source project hosting and collaboration platform used by development teams. A cross-site scripting (XSS) vulnerability in the code display feature allows attackers to inject malicious scripts that could execute in users' browsers when viewing code, potentially stealing session tokens or performing unauthorized actions on behalf of users.

Technologies: Apache Allura. Vendors: Apache.

Quick answers

Is CVE-2026-73238 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-73238 being exploited in the wild.
How severe is CVE-2026-73238?
Medium severity, with a CVSS score of 6.1, published 12 August 2026.
Which products and versions are affected?
Apache Allura before 1.19.1.
Is there a fix for CVE-2026-73238?
A patch was published on 2026-06-29: Fixed in version 1.19.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-73238 attacked?
It is attacked over the network.
Am I affected by CVE-2026-73238?
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.

Technical details

This is a cross-site scripting (XSS) vulnerability in the code display component of Apache Allura. The vulnerability allows injection of malicious JavaScript that executes in the context of a user's browser when viewing code repositories or files. The attack vector is network-based and does not require authentication to trigger in typical XSS scenarios. An attacker can exploit this to steal session cookies, perform actions on behalf of logged-in users, or redirect users to malicious sites. The vulnerability affects Apache Allura before version 1.19.1, which contains the fix.

Affected products

  • Apache Allura before 1.19.1

Timeline

  • 2026-06-29: disclosed
  • 2026-06-29: patched: Fixed in version 1.19.1

References

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