CVE-2026-32471

HIGHPre-NVD 8.58.5
EchelonGraph scoreHIGH confidence

Score 8.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. a secondary CVSS source baseline 8.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.5Exploit: None knownExposed: 0

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

Subscriber SQL Injection in ProLancer Element <= 1.4.8 versions.

CVSS v3
8.5
EG Score
8.5(high)
EG Risk
38(Track)
EG Risk 38/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
Severity85% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

August 24, 2026

Last Modified

August 24, 2026

Advisory Details (1)

Auto-updated Aug 24, 2026
Patch available.

Vendor Advisories for CVE-2026-32471(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 28× in last 7d / 28× 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-30 01:31 UTCEG score recompute
  2. 2026-08-30 01:31 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 13:02 UTCGHSA enrichment
  5. 2026-08-29 00:27 UTCEG score recompute
  6. 2026-08-29 00:27 UTCGHSA enrichment
  7. 2026-08-28 21:41 UTCEPSS rescore
  8. 2026-08-28 08:08 UTCGHSA enrichment
  9. 2026-08-27 19:39 UTCEG score recompute
  10. 2026-08-27 19:39 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 07:10 UTCGHSA enrichment
  13. 2026-08-26 18:40 UTCEG score recompute
  14. 2026-08-26 18:40 UTCGHSA enrichment
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-26 06:11 UTCGHSA enrichment
  17. 2026-08-25 17:42 UTCEG score recompute
  18. 2026-08-25 17:42 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 05:13 UTCGHSA enrichment
  21. 2026-08-24 16:45 UTCGHSA enrichment
  22. 2026-08-24 13:28 UTCEG score recompute
  23. 2026-08-24 13:28 UTCGHSA enrichment
  24. 2026-08-24 12:58 UTCEG score recompute
  25. 2026-08-24 12:58 UTCGHSA enrichment
Show 3 more
  1. 2026-08-24 12:21 UTCEG score recompute
  2. 2026-08-24 12:02 UTCEG score recompute
  3. 2026-08-24 12:00 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-32471?
CVE-2026-32471 is a high vulnerability published on August 24, 2026. Subscriber SQL Injection in ProLancer Element <= 1.4.8 versions.
When was CVE-2026-32471 disclosed?
CVE-2026-32471 was first published in the National Vulnerability Database on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32471 actively exploited?
CVE-2026-32471 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 80.2% of all scored CVEs.
What is the CVSS score of CVE-2026-32471?
CVE-2026-32471 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-32471?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32471, 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-32471

Explore →

Is Your Infrastructure Affected by CVE-2026-32471?

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