CVE-2026-84301

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (21st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-84559 (ENISA EUVD)Source: ENISA EUVD

6.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

FastGPT is an open-source LLM platform for building AI applications on a knowledge base. Prior to 4.15.2, the safe Axios request interceptor in packages/service/common/api/axios.ts validates a hostname with isInternalAddress() before a later HTTP connection performs an independent DNS lookup, creating a DNS rebinding window, allowing an attacker-controlled hostname to resolve publicly during the check and to a loopback, private, link-local, or metadata address during connection. An authenticated attacker who can supply a URL to a safe-Axios-backed HTTP tool, workflow HTTP node, external file fetch, or other server-side integration can use this time-of-check/time-of-use gap to reach services that direct private-address inputs would block. The same independent re-resolution occurs after manual redirect hops because each redirect target is checked before a separate connection lookup. This issue is fixed in version 4.15.2.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 22, 2026

Last Modified

September 26, 2026

Advisory Details (4)

Auto-updated Sep 22, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

v4.15.2

Patch available: labring/FastGPT v4.15.2

https://github.com/labring/FastGPT/releases/tag/v4.15.2
GitHub commit

commit 0a38565c9d1f (labring/FastGPT)

Fix landed in labring/FastGPT commit 0a38565c9d1f — awaiting tagged release

https://github.com/labring/FastGPT/commit/0a38565c9d1f790045636bd9d55f8d2296c938c7
GitHub pull request

fix: pin DNS for safe axios direct requests

Fix merged in labring/FastGPT PR #7261 on 2026-07-06 — awaiting tagged release

https://github.com/labring/FastGPT/pull/7261
GitHub advisoryMentions a patch (unverified)

FastGPT safe axios SSRF guard still allows DNS rebinding TOCTOU on protected outbound requests · Advisory · labring/FastGPT · GitHub

https://github.com/labring/FastGPT/security/advisories/GHSA-6jwp-qf29-hpj9

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-10-30 00:55 UTCOSV refresh
  5. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-25 13:56 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-22 13:15 UTCEG score recompute
  15. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-10-18 03:06 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  24. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  25. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
Show 42 more
  1. 2026-10-12 14:53 UTCEG score recompute
  2. 2026-10-11 19:18 UTCEG score recompute
  3. 2026-10-11 16:35 UTCEG score recompute
  4. 2026-10-11 13:52 UTCEG score recompute
  5. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-11 01:42 UTCEG score recompute
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-10-10 00:57 UTCEG score recompute
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-09 00:56 UTCEG score recompute
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-08 00:55 UTCEG score recompute
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-07 00:53 UTCEG score recompute
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-06 00:45 UTCEG score recompute
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-05 00:44 UTCEG score recompute
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-10-04 00:40 UTCEG score recompute
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-10-03 00:39 UTCEG score recompute
  23. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  24. 2026-10-02 00:37 UTCEG score recompute
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  26. 2026-10-01 00:36 UTCEG score recompute
  27. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  28. 2026-09-30 00:35 UTCEG score recompute
  29. 2026-09-29 00:28 UTCEG score recompute
  30. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  31. 2026-09-28 00:26 UTCEG score recompute
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  33. 2026-09-27 00:25 UTCEG score recompute
  34. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  35. 2026-09-26 00:23 UTCEG score recompute
  36. 2026-09-25 23:49 UTCEG score recompute
  37. 2026-09-24 17:59 UTCEG score recompute
  38. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  39. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  40. 2026-09-22 17:34 UTCEG score recompute
  41. 2026-09-22 16:58 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
  42. 2026-09-22 16:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)· as of November 1, 2026

Frequently asked(5)

What is CVE-2026-84301?
CVE-2026-84301 is a medium-severity vulnerability; its CVE record was published on September 22, 2026. FastGPT is an open-source LLM platform for building AI applications on a knowledge base. Prior to 4.15.2, the safe Axios request interceptor in packages/service/common/api/axios.ts validates a hostname with isInternalAddress() before a later HTTP connection performs an independent DNS lookup,…
When was the CVE record for CVE-2026-84301 published?
The CVE record for CVE-2026-84301 was published on September 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 26, 2026; the record at its source may have been updated since.
Is CVE-2026-84301 actively exploited?
CVE-2026-84301 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84301?
CVE-2026-84301 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-84301?
A fix for CVE-2026-84301 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-84301?

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

Book a Demo →Browse All CVEs