CVE-2026-73238

MEDIUMPre-NVD 6.16.1—
EchelonGraph scoreHIGH confidence

Score 6.1 from GitHub Security Advisory published 2026-08-12. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.1
EG Score
6.1(high)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity61% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

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

http://www.openwall.com/lists/oss-security/2026/08/12/17
generic
https://lists.apache.org/thread/bbzhnvqlwvwbprnfg4g41s8wkc5bdfmk
generic

Apache Allura 1.19.1 released, with many security fixes

https://allura.apache.org/posts/2026-allura-1.19.1.html

Vendor Advisories for CVE-2026-73238(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 20:31 UTCGHSA enrichment
  2. 2026-08-19 20:12 UTCEG score recompute
  3. 2026-08-19 20:12 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 19:48 UTCEG score recompute
  6. 2026-08-18 19:48 UTCGHSA enrichment
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-17 19:28 UTCEG score recompute
  10. 2026-08-17 19:28 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 22:23 UTCEG score recompute
  13. 2026-08-16 22:23 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:15 UTCEPSS rescore
  17. 2026-08-15 22:03 UTCEG score recompute
  18. 2026-08-15 22:03 UTCGHSA enrichment
  19. 2026-08-15 01:31 UTCEPSS rescore
  20. 2026-08-14 21:43 UTCEG score recompute
  21. 2026-08-14 21:43 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 21:23 UTCEG score recompute
  24. 2026-08-13 21:23 UTCGHSA enrichment
  25. 2026-08-12 21:01 UTCGHSA enrichment
Show 9 more
  1. 2026-08-12 20:19 UTCEG score recompute▲ 6.10
  2. 2026-08-12 20:19 UTCGHSA enrichment
  3. 2026-08-12 20:19 UTCNVD updateCVSS v3 → 6.1 · severity → MEDIUM
  4. 2026-08-12 19:19 UTCGHSA enrichment
  5. 2026-08-12 19:18 UTCNVD update
  6. 2026-08-12 18:30 UTCMITRE cvelistV5
  7. 2026-08-12 17:35 UTCNVD update
  8. 2026-08-12 17:06 UTCEG score recompute
  9. 2026-08-12 17:05 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73238?
CVE-2026-73238 is a medium vulnerability published on 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.
When was CVE-2026-73238 disclosed?
CVE-2026-73238 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73238 actively exploited?
CVE-2026-73238 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.0% of all scored CVEs.
What is the CVSS score of CVE-2026-73238?
CVE-2026-73238 has a CVSS v3.1 base score of 6.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-73238?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73238, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73238

Explore →

Is Your Infrastructure Affected by CVE-2026-73238?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs