CVE-2026-96429

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (18th percentile of EPSS-scored CVEs). 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 — 4 sources updated this week
9.3EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.3Exploit: None knownExposed services: Not assessed

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

SQL Injection in the /WebAgenda/SMBAjaxConfigProcess.do API endpoint of Flowring Agentflow 4.0 version before 2025/08/08 allows remote attackers to execute arbitrary SQL commands via the id parameter.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
57
EG Risk 57/100CISA SSVC

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
Severity93% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2026

Last Modified

September 29, 2026

Advisory Details (1)

Auto-updated Oct 3, 2026
No patch confirmed yet.
generic

Advisory | ZUSO Generation 如梭世代

https://zuso.ai/cve-advisory/advisory

Vendor Advisories for CVE-2026-96429(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 46× in last 7d / 46× 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-10-04 15:00 UTCGHSA enrichment
  2. 2026-10-04 11:07 UTCGHSA enrichment
  3. 2026-10-04 07:15 UTCGHSA enrichment
  4. 2026-10-04 03:23 UTCGHSA enrichment
  5. 2026-10-03 23:31 UTCGHSA enrichment
  6. 2026-10-03 19:39 UTCGHSA enrichment
  7. 2026-10-03 15:47 UTCEG score recompute
  8. 2026-10-03 15:46 UTCGHSA enrichment
  9. 2026-10-03 14:26 UTCEPSS rescore
  10. 2026-10-03 11:48 UTCGHSA enrichment
  11. 2026-10-03 07:56 UTCGHSA enrichment
  12. 2026-10-03 04:00 UTCGHSA enrichment
  13. 2026-10-03 00:07 UTCGHSA enrichment
  14. 2026-10-02 20:14 UTCEG score recompute
  15. 2026-10-02 20:14 UTCGHSA enrichment
  16. 2026-10-02 17:57 UTCEPSS rescore
  17. 2026-10-02 16:18 UTCGHSA enrichment
  18. 2026-10-02 12:26 UTCGHSA enrichment
  19. 2026-10-02 08:34 UTCGHSA enrichment
  20. 2026-10-02 04:42 UTCGHSA enrichment
  21. 2026-10-02 00:49 UTCGHSA enrichment
  22. 2026-10-01 20:55 UTCEG score recompute
  23. 2026-10-01 20:55 UTCGHSA enrichment
  24. 2026-10-01 19:51 UTCEPSS rescore
  25. 2026-10-01 17:00 UTCGHSA enrichment
Show 21 more
  1. 2026-10-01 13:02 UTCGHSA enrichment
  2. 2026-10-01 09:10 UTCGHSA enrichment
  3. 2026-10-01 05:18 UTCGHSA enrichment
  4. 2026-10-01 01:26 UTCGHSA enrichment
  5. 2026-09-30 21:34 UTCGHSA enrichment
  6. 2026-09-30 17:32 UTCEG score recompute
  7. 2026-09-30 17:32 UTCGHSA enrichment
  8. 2026-09-30 15:04 UTCEPSS rescore
  9. 2026-09-30 13:39 UTCGHSA enrichment
  10. 2026-09-30 09:47 UTCGHSA enrichment
  11. 2026-09-30 05:55 UTCGHSA enrichment
  12. 2026-09-30 02:02 UTCGHSA enrichment
  13. 2026-09-29 22:10 UTCGHSA enrichment
  14. 2026-09-29 17:33 UTCEG score recompute
  15. 2026-09-29 17:33 UTCGHSA enrichment
  16. 2026-09-29 16:54 UTCEG score recompute
  17. 2026-09-29 16:54 UTCGHSA enrichment
  18. 2026-09-29 13:20 UTCGHSA enrichment
  19. 2026-09-29 09:25 UTCEG score recompute
  20. 2026-09-29 08:44 UTCEG score recompute
  21. 2026-09-29 08:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-96429?
CVE-2026-96429 is a critical vulnerability published on September 29, 2026. SQL Injection in the /WebAgenda/SMBAjaxConfigProcess.do API endpoint of Flowring Agentflow 4.0 version before 2025/08/08 allows remote attackers to execute arbitrary SQL commands via the id parameter.
When was CVE-2026-96429 disclosed?
CVE-2026-96429 was first published on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-96429 actively exploited?
CVE-2026-96429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96429?
CVE-2026-96429 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-96429?
No fix for CVE-2026-96429 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-96429 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-96429?

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