CVE-2026-85030

LOWPre-NVD 3.73.7
EchelonGraph scoreHIGH confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-09-03. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: Elevated riskExposed: 0

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

A vulnerability has been found in HKUDS AI-Trader up to d03ff6c056b32ced735adf7c19ed8175adb1c8df. The affected element is an unknown function of the file service/server/routes_agent.py of the component selfRegister API Endpoint. Such manipulation of the argument initial_balance leads to business logic errors. The attack may be launched remotely. This attack is characterized by high complexity. The exploitability is described as difficult. The exploit has been disclosed to the public and may be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. profit_percent_for_display() divides by INITIAL_CAPITAL + deposited, and challenge scoring's return_pct also normalises against the attacker-inflated starting_cash. So an inflated initial_balance does not yield artificial percent returns - it inflates the absolute cash/equity column only, which is a cosmetic/leaderboard-gaming concern in a simulated game.

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

Published

September 3, 2026

Last Modified

September 5, 2026

Vendor Advisories for CVE-2026-85030(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 12× in last 7d / 32× 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-09-18 22:11 UTCEG score recompute
  2. 2026-09-18 22:11 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-16 14:09 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-16 03:36 UTCEG score recompute
  8. 2026-09-16 03:36 UTCGHSA enrichment
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-13 09:01 UTCEG score recompute
  12. 2026-09-13 09:01 UTCGHSA enrichment
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-10 14:27 UTCEG score recompute
  16. 2026-09-10 14:27 UTCGHSA enrichment
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 19:52 UTCEG score recompute
  19. 2026-09-07 19:52 UTCGHSA enrichment
  20. 2026-09-06 13:48 UTCEPSS rescore
  21. 2026-09-05 15:31 UTCEPSS rescore
  22. 2026-09-05 01:21 UTCNVD updateCVSS v4 → 2.9
  23. 2026-09-05 01:18 UTCEG score recompute
  24. 2026-09-05 01:17 UTCGHSA enrichment
  25. 2026-09-05 01:14 UTCMITRE cvelistV5CVSS v4 → 6.3
Show 7 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-03 17:39 UTCEG score recompute
  3. 2026-09-03 17:39 UTCGHSA enrichment
  4. 2026-09-03 13:15 UTCEG score recompute
  5. 2026-09-03 13:13 UTCNVD updateCVSS v4 → 2.9
  6. 2026-09-03 01:41 UTCEG score recompute
  7. 2026-09-03 01:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-85030?
CVE-2026-85030 is a low vulnerability published on September 3, 2026. A vulnerability has been found in HKUDS AI-Trader up to d03ff6c056b32ced735adf7c19ed8175adb1c8df. The affected element is an unknown function of the file service/server/routesagent.py of the component selfRegister API Endpoint. Such manipulation of the argument initialbalance leads to business…
When was CVE-2026-85030 disclosed?
CVE-2026-85030 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-85030 actively exploited?
CVE-2026-85030 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-85030?
CVE-2026-85030 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-85030?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-85030, 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-85030

Explore →

Is Your Infrastructure Affected by CVE-2026-85030?

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