{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-73237 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-73237 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-73237 is a medium-severity cross-site scripting vulnerability in Apache Allura, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-73237 and fix it if it is affected.\n\nWhat it is: CVE-2026-73237 is a medium-severity cross-site scripting vulnerability in Apache Allura, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-73237 in the wild and no public exploit code.\n\nAffected product: Apache Allura. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-73237/ (Markdown: https://insights.sbomify.com/CVE-2026-73237/index.md)","id":"CVE-2026-73237","markdown":"https://insights.sbomify.com/CVE-2026-73237/index.md","name":"CVE-2026-73237","record":{"aliases":["GHSA-q6fp-vfv9-v477"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Allura","requires_auth":"none","summary":"Attackers can inject malicious scripts via Markdown, potentially stealing user sessions or executing code in Apache Allura.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"allura","vendor":"apache"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-80","name":"Improper Neutralization of Script-Related HTML Tags in a Web Page"}],"description":"XSS vulnerability in Markdown handling in Apache Allura.\n\nThis issue affects Apache Allura: from 1.10.0 before 1.19.1.\n\nUsers are recommended to upgrade to version 1.19.1, which fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Apache Allura: XSS in markdown pipeline","id":"CVE-2026-73237","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Apache Allura: XSS in code display","id":"CVE-2026-73238"},"packages":[],"prev":{"headline":"Apache Syncope: Cross-Realm authorization bypass in delegated administration","id":"CVE-2026-73236"},"products":["Apache Allura"],"published":"2026-08-12","related":[{"cvss_score":9.8,"headline":"Apache Allura: Git command injection","id":"CVE-2026-73240","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":9.1,"headline":"Apache Allura: Server-side request forgery","id":"CVE-2026-69223","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":7.5,"headline":"Apache Allura: sensitive information exposure via DNS rebinding","id":"CVE-2024-36471","kev_date_added":null,"published":"2024-06-10"},{"cvss_score":7.5,"headline":"Path traversal in Apache Allura","id":"CVE-2018-1299","kev_date_added":null,"published":"2018-02-06"},{"cvss_score":6.5,"headline":"Apache Allura: Missing permission checks IDOR","id":"CVE-2026-73239","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":6.1,"headline":"Apache Allura: XSS in code display","id":"CVE-2026-73238","kev_date_added":null,"published":"2026-08-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-12","vendors":["Apache Software Foundation"]},"summary":"Attackers can inject malicious scripts via Markdown, potentially stealing user sessions or executing code in Apache Allura.","url":"https://insights.sbomify.com/CVE-2026-73237/"}