Apache Allura
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Apache Allura.
By the Year
In 2026 there have been 6 vulnerabilities in Apache Allura with an average score of 7.2 out of ten. Allura did not have any published security vulnerabilities last year. That is, 6 more vulnerabilities have already been reported in 2026 as compared to last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 6 | 7.15 |
| 2025 | 0 | 0.00 |
| 2024 | 2 | 4.80 |
| 2023 | 1 | 4.90 |
| 2022 | 0 | 0.00 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 1 | 6.10 |
| 2018 | 2 | 6.80 |
It may take a day or so for new Allura vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Apache Allura Security Vulnerabilities
Unauth REST Disclosure in Apache Allura <=1.19.1
CVE-2026-75099
5.3 - Medium
- August 24, 2026
Unauthenticated REST disclosure of certain content items in Apache Allura. This issue affects Apache Allura: through 1.19.1. Users are recommended to upgrade to version 1.20.0, which fixes the issue.
Information Disclosure
XSS in Markdown Handling in Apache Allura 1.10.0-1.19.0
CVE-2026-73237
6.1 - Medium
- August 12, 2026
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.
Basic XSS
XSS in Code Display of Apache Allura <1.19.1
CVE-2026-73238
6.1 - Medium
- August 12, 2026
XSS vulnerability in code display in Apache Allura. This issue affects Apache Allura: before 1.19.1. Users are recommended to upgrade to version 1.19.1, which fixes the issue.
Basic XSS
Apache Allura IDOR via Artifact Types (before 1.19.1)
CVE-2026-73239
6.5 - Medium
- August 12, 2026
Insecure Direct Object Reference (IDOR) due to missing permission checks for multiple Artifact types in Apache Allura. This issue affects Apache Allura: before 1.19.1. Users are recommended to upgrade to version 1.19.1, which fixes the issue.
Improper Handling of Insufficient Permissions or Privileges
Apache Allura <1.19.1: git Arg Injt via crafted inputs
CVE-2026-73240
9.8 - Critical
- August 12, 2026
Specifically crafted inputs may lead to git argument injection in Apache Allura. This issue affects Apache Allura: before 1.19.1. Users are recommended to upgrade to version 1.19.1, which fixes the issue.
Argument Injection
Apache Allura SSRF via Webhooks before 1.19.1
CVE-2026-69223
9.1 - Critical
- August 11, 2026
Apache Allura's webhooks are vulnerable to Server-Side Request Forgery (SSRF). This issue affects Apache Allura: before 1.19.1. Users are recommended to upgrade to version 1.19.1, which fixes the issue.
SSRF
Apache Allura Neighborhood Settings XSS (v1.4.0-1.17.0)
CVE-2024-38379
4.8 - Medium
- June 22, 2024
Apache Allura's neighborhood settings are vulnerable to a stored XSS attack. Only neighborhood admins can access these settings, so the scope of risk is limited to configurations where neighborhood admins are not fully trusted. This issue affects Apache Allura: from 1.4.0 through 1.17.0. Users are recommended to upgrade to version 1.17.1, which fixes the issue.
XSS
Apache Allura v1.0.1-1.16.0 DNS Rebinding Vulnerability in Import Component
CVE-2024-36471
- June 10, 2024
Import functionality is vulnerable to DNS rebinding attacks between verification and processing of the URL. Project administrators can run these imports, which could cause Allura to read from internal services and expose them. This issue affects Apache Allura from 1.0.1 through 1.16.0. Users are recommended to upgrade to version 1.17.0, which fixes the issue. If you are unable to upgrade, set "disable_entry_points.allura.importers = forge-tracker, forge-discussion" in your .ini config file.
Information Disclosure
Apache Allura <1.16: allura.importers URL injection reads local FS
CVE-2023-46851
4.9 - Medium
- November 07, 2023
Allura Discussion and Allura Forum importing does not restrict URL values specified in attachments. Project administrators can run these imports, which could cause Allura to read local files and expose them. Exposing internal files then can lead to other exploits, like session hijacking, or remote code execution. This issue affects Apache Allura from 1.0.1 through 1.15.0. Users are recommended to upgrade to version 1.16.0, which fixes the issue. If you are unable to upgrade, set "disable_entry_points.allura.importers = forge-tracker, forge-discussion" in your .ini config file.
In Apache Allura prior to 1.11.0, a vulnerability exists for stored XSS on the user dropdown selector when creating or editing tickets
CVE-2019-10085
6.1 - Medium
- June 19, 2019
In Apache Allura prior to 1.11.0, a vulnerability exists for stored XSS on the user dropdown selector when creating or editing tickets. The XSS executes when a user engages with that dropdown on that page.
XSS
In Apache Allura prior to 1.8.1, attackers may craft URLs that cause HTTP response splitting
CVE-2018-1319
6.1 - Medium
- March 15, 2018
In Apache Allura prior to 1.8.1, attackers may craft URLs that cause HTTP response splitting. If a victim goes to a maliciously crafted URL, unwanted results may occur including XSS or service denial for the victim's browsing session.
Injection
In Apache Allura before 1.8.0, unauthenticated attackers may retrieve arbitrary files through the Allura web application
CVE-2018-1299
7.5 - High
- February 06, 2018
In Apache Allura before 1.8.0, unauthenticated attackers may retrieve arbitrary files through the Allura web application. Some webservers used with Allura, such as Nginx, Apache/mod_wsgi or paster may prevent the attack from succeeding. Others, such as gunicorn do not prevent it and leave Allura vulnerable.
Directory traversal
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Apache Allura or by Apache? Click the Watch button to subscribe.
