CVE-2026-71502

MEDIUMPre-NVD 5.15.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 49% 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
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.1Exploit: None knownExposed: 0

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

CTI-Transmute contains a stored cross-site scripting vulnerability caused by insufficient neutralization of Vue template expression delimiters in server-rendered user-controlled data.

An unauthenticated attacker can create a public conversion whose name or description contains a malicious Vue expression using the application's configured [[ ... ]] delimiters. User profile names may provide an additional injection vector. Although Jinja HTML escaping is applied, the resulting value is subsequently included in a DOM region compiled by Vue.

Vue interprets the attacker-controlled value as a template expression rather than ordinary text. By accessing the JavaScript Function constructor from within the expression, an attacker can execute arbitrary JavaScript in the security context of the CTI-Transmute origin. The application's nonce-based Content Security Policy does not prevent exploitation because the Vue runtime compiler requires the unsafe-eval policy exception.

The malicious payload is stored by the application and executed whenever another user opens an affected page, such as the public conversion detail page. The victim may be a normal user or an administrator. Successful exploitation could allow the attacker to:

* Access data available to the victim through the application. * Extract API keys, tokens, or other sensitive information exposed to the page. * Perform authenticated actions using the victim's session. * Modify conversions or other application data. * Escalate the impact by targeting an administrator.

A demonstrated payload can use [].constructor.constructor(...) to obtain the JavaScript Function constructor and execute arbitrary code. The regression tests also show that a short first-stage payload could retrieve an uncapped conversion description and evaluate a larger second-stage payload.

The patch addresses the vulnerability by registering a global Jinja finalize hook that inserts a zero-width Unicode word joiner inside every Vue delimiter found in server-rendered values. This prevents Vue from recognizing the values as template expressions while preserving their visible representation.

CVSS v3
5.1
EG Score
5.1(medium)
EG Risk
23(Track)
EG Risk 23/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
Severity51% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 8, 2026

Vendor Advisories for CVE-2026-71502(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 44× 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 07:56 UTCEG score recompute
  2. 2026-08-21 07:56 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 09:04 UTCEG score recompute
  5. 2026-08-20 09:04 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 10:12 UTCEG score recompute
  8. 2026-08-19 10:12 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 11:15 UTCEG score recompute
  12. 2026-08-18 11:15 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 12:15 UTCEG score recompute
  15. 2026-08-17 12:15 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 13:24 UTCEG score recompute
  19. 2026-08-16 13:24 UTCGHSA enrichment
  20. 2026-08-16 02:15 UTCEPSS rescore
  21. 2026-08-15 14:33 UTCEG score recompute
  22. 2026-08-15 14:33 UTCGHSA enrichment
  23. 2026-08-15 01:31 UTCEPSS rescore
  24. 2026-08-14 15:41 UTCEG score recompute
  25. 2026-08-14 15:41 UTCGHSA enrichment
Show 19 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 16:49 UTCGHSA enrichment
  3. 2026-08-12 17:57 UTCEG score recompute
  4. 2026-08-12 17:57 UTCGHSA enrichment
  5. 2026-08-12 13:51 UTCEPSS rescore
  6. 2026-08-11 19:06 UTCEG score recompute
  7. 2026-08-11 19:05 UTCGHSA enrichment
  8. 2026-08-11 00:00 UTCEPSS rescore
  9. 2026-08-10 20:12 UTCGHSA enrichment
  10. 2026-08-09 21:20 UTCEG score recompute
  11. 2026-08-09 21:20 UTCGHSA enrichment
  12. 2026-08-09 13:47 UTCEPSS rescore
  13. 2026-08-08 22:29 UTCEG score recompute
  14. 2026-08-08 21:17 UTCEG score recompute
  15. 2026-08-08 16:37 UTCEPSS rescore
  16. 2026-08-08 13:05 UTCEG score recompute
  17. 2026-08-07 14:13 UTCEG score recompute
  18. 2026-08-06 22:16 UTCEG score recompute
  19. 2026-08-06 22:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-71502?
CVE-2026-71502 is a medium vulnerability published on August 6, 2026. CTI-Transmute contains a stored cross-site scripting vulnerability caused by insufficient neutralization of Vue template expression delimiters in server-rendered user-controlled data. An unauthenticated attacker can create a public conversion whose name or description contains a malicious Vue…
When was CVE-2026-71502 disclosed?
CVE-2026-71502 was first published in the National Vulnerability Database on August 6, 2026, with the most recent update on August 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71502 actively exploited?
CVE-2026-71502 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.4% of all scored CVEs.
What is the CVSS score of CVE-2026-71502?
CVE-2026-71502 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-71502?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71502, 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-71502

Explore →

Is Your Infrastructure Affected by CVE-2026-71502?

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