allura vulnerabilities and fixes
Recent CVEs affecting allura, with upgrade or downgrade steps. 5 tracked.
allura has 5 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 5. Most recent: 2026-08-12. Highest priority: CVE-2026-73240 (score 63/100).
- CVE-2026-73240 CRITICAL 9.8 UPGRADE Specifically crafted inputs may lead to git argument injection in Apache Allura. This issue affects Apache Al
- CVE-2026-69223 CRITICAL 9.1 UPGRADE Apache Allura's webhooks are vulnerable to Server-Side Request Forgery (SSRF). This issue affects Apache Allu
- CVE-2026-73237 MEDIUM 6.1 UPGRADE XSS vulnerability in Markdown handling in Apache Allura. This issue affects Apache Allura: from 1.10.0 before
- CVE-2026-73238 MEDIUM 6.1 UPGRADE XSS vulnerability in code display in Apache Allura. This issue affects Apache Allura: before 1.19.1. Users a
- CVE-2026-73239 MEDIUM 6.5 UPGRADE Insecure Direct Object Reference (IDOR) due to missing permission checks for multiple Artifact types in Apache
FAQ
How do I fix allura vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is allura being exploited right now?
None of the tracked allura CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which allura CVE should I patch first?
CVE-2026-73240 currently ranks highest (63/100): Specifically crafted inputs may lead to git argument injection in Apache Allura. This issue affects Apache Al.