CVE-2026-73374

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
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.

A stored cross-site scripting (XSS) vulnerability existed in Vulnerability-Lookup in the render_tag_badges Jinja filter used to display reference tags associated with vulnerability records.

Values from containers.cna.references[].tags[] were directly interpolated into HTML badge elements and the resulting string was wrapped in markupsafe.Markup. Because Markup marks the generated content as safe, Jinja's automatic HTML escaping was bypassed.

An authenticated user with permissions to create or modify vulnerability records, such as a user holding the vulnerability:create or vulnerability:modify permission, could submit a crafted reference tag through the CNA API containing arbitrary HTML or JavaScript-capable markup.

The malicious value would subsequently be stored as part of the vulnerability record. When another user visited the corresponding public /cve/ or /vuln/ page, the crafted tag would be rendered as HTML in the viewer's browser. This could result in JavaScript execution in the security context of the Vulnerability-Lookup application.

Successful exploitation could allow an attacker to perform actions in the context of a victim, access information available to the victim's browser session, or modify page content. As the affected vulnerability pages can be accessed publicly, exploitation may affect users who are not authenticated.

The issue was corrected by applying markupsafe.escape() to each reference tag before inserting it into the HTML badge markup, while retaining Markup only for the static HTML scaffolding.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
28(Track)
EG Risk 28/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 12, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit d29901655c50 (vulnerability-lookup/vulnerability-lookup)

Fix landed in vulnerability-lookup/vulnerability-lookup commit d29901655c50 — awaiting tagged release

https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d29901655c50cf3c25737d9ea86180268df51b57

Vendor Advisories for CVE-2026-73374(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 25× 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-21 03:27 UTCEG score recompute
  2. 2026-08-21 03:27 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 05:09 UTCEG score recompute
  5. 2026-08-20 05:09 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 06:50 UTCEG score recompute
  8. 2026-08-19 06:50 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 08:32 UTCEG score recompute
  12. 2026-08-18 08:32 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 10:10 UTCEG score recompute
  15. 2026-08-17 10:10 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 11:52 UTCEG score recompute
  19. 2026-08-16 11:52 UTCGHSA enrichment
  20. 2026-08-16 02:15 UTCEPSS rescore
  21. 2026-08-15 13:34 UTCEG score recompute
  22. 2026-08-15 13:34 UTCGHSA enrichment
  23. 2026-08-15 01:31 UTCEPSS rescore
  24. 2026-08-14 15:15 UTCEG score recompute
  25. 2026-08-14 15:15 UTCGHSA enrichment
Show 9 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 16:56 UTCGHSA enrichment
  3. 2026-08-12 18:38 UTCEG score recompute
  4. 2026-08-12 18:38 UTCGHSA enrichment
  5. 2026-08-12 17:26 UTCEG score recompute
  6. 2026-08-12 17:26 UTCGHSA enrichment
  7. 2026-08-12 15:26 UTCEG score recompute
  8. 2026-08-12 14:29 UTCEG score recompute
  9. 2026-08-12 14:28 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73374?
CVE-2026-73374 is a medium vulnerability published on August 12, 2026. A stored cross-site scripting (XSS) vulnerability existed in Vulnerability-Lookup in the rendertagbadges Jinja filter used to display reference tags associated with vulnerability records. Values from containers.cna.references[].tags[] were directly interpolated into HTML badge elements and the…
When was CVE-2026-73374 disclosed?
CVE-2026-73374 was first published in the National Vulnerability Database on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73374 actively exploited?
CVE-2026-73374 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 70.8% of all scored CVEs.
What is the CVSS score of CVE-2026-73374?
CVE-2026-73374 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-73374?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73374, 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-73374

Explore →

Is Your Infrastructure Affected by CVE-2026-73374?

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