Skip to main content
VulnerabilityPublished

CVE-2026-73237: Apache Allura · Basic XSS

Affects Apache AlluraSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 1.19.1 when convenient.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.19.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade Apache Allura and org.apache.allura/allura to 1.19.1.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache AlluraAffected
  • >=1.10.0 <1.19.1
Fixed in
  • 1.19.1
Mavenorg.apache.allura/allurapkg:maven/org.apache.allura/alluraOther threatsAffected
  • <1.19.1
Fixed in
  • 1.19.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache Allura to version 1.19.1 or later, which contains the fix for this XSS vulnerability. Patch status is confirmed by the vendor's recommendation to upgrade. No other mitigation or temporary workaround is indicated.

Description

XSS vulnerability in Markdown handling in Apache Allura. This issue affects Apache Allura: from 1.10.0 before 1.19.1. Users are recommended to upgrade to version 1.19.1, which fixes the issue.

References

Community reviews

Loading reviews…