Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.
CVE-2026-75336
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-27. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 75(Attend)EG Risk 75/100SSVC: Attend
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 computedSeverity98% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 27, 2026
Advisory Details (1)
Auto-updated Aug 27, 2026CVE/funiture/SQL Injection.md at main · fangtang7/CVE · GitHub
https://github.com/fangtang7/CVE/blob/main/funiture/SQL%20Injection.mdVendor Advisories for CVE-2026-75336(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 29× in last 7d / 29× 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.
- 2026-08-30 05:17 UTCGHSA enrichment
- 2026-08-30 01:39 UTCEG score recompute
- 2026-08-30 01:39 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 22:00 UTCGHSA enrichment
- 2026-08-29 18:21 UTCGHSA enrichment
- 2026-08-29 14:40 UTCGHSA enrichment
- 2026-08-29 11:02 UTCGHSA enrichment
- 2026-08-29 07:22 UTCGHSA enrichment
- 2026-08-29 03:40 UTCGHSA enrichment
- 2026-08-28 23:59 UTCEG score recompute
- 2026-08-28 23:59 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 16:05 UTCGHSA enrichment
- 2026-08-28 11:47 UTCGHSA enrichment
- 2026-08-28 08:08 UTCGHSA enrichment
- 2026-08-28 04:27 UTCGHSA enrichment
- 2026-08-28 00:48 UTCGHSA enrichment
- 2026-08-27 21:09 UTCEG score recompute
- 2026-08-27 21:09 UTCGHSA enrichment
- 2026-08-27 17:31 UTCEG score recompute
- 2026-08-27 17:31 UTCGHSA enrichment
- 2026-08-27 16:52 UTCEG score recompute▲ 9.80
- 2026-08-27 16:51 UTCGHSA enrichment
- 2026-08-27 16:43 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
Show 4 moreShow fewer
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 23:20 UTCNVD update
- 2026-08-26 23:10 UTCEG score recompute
- 2026-08-26 23:09 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-75336?
When was CVE-2026-75336 disclosed?
Is CVE-2026-75336 actively exploited?
What is the CVSS score of CVE-2026-75336?
How do I remediate CVE-2026-75336?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75336
Is Your Infrastructure Affected by CVE-2026-75336?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.