CVE-2026-50561

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (52nd 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

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

9.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Yuxi is a large-model-based intelligent knowledge base and knowledge graph agent development platform. Prior to version 0.6.2, the project's authentication mechanism contains a flaw. In affected versions, the system does not sufficiently validate the identity token in the Authorization header — only performing a validity check. This allows an administrator token generated in another deployment instance or local testing environment to be used to access the backend management interfaces of a different affected instance. An attacker who obtains or constructs an acceptable administrator Authorization token may bypass normal login authentication and gain administrator privileges. This vulnerability could allow an attacker to access system configurations, invoke backend management APIs, create administrator accounts, and ultimately take over the system backend. This issue has been fixed in version 0.6.2. Before upgrading, users are advised to implement the following temporary measures: Set the environment variable JWT_SECRET_KEY to a non-default value, and configure a unique, sufficiently strong JWT/authentication key for each deployment instance; and/or avoid exposing backend management interfaces directly to the public network.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
58
EG Risk 58/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)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
52nd
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 (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-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.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

August 12, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Oct 2, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

JWT 身份认证绕过导致跨实例管理员令牌复用 · Advisory · xerrors/Yuxi · GitHub

Affected: version 0.6.2.

https://github.com/xerrors/Yuxi/security/advisories/GHSA-6959-99pq-c56x
Web page

Error: 存在身份认证绕过漏洞 · Issue #673 · xerrors/Yuxi · GitHub

https://github.com/xerrors/Yuxi/issues/673
GitHub commit Patch Available

commit 1e8b20e30b12 (xerrors/Yuxi)

Patch available: xerrors/Yuxi v0.7.0 (contains commit 1e8b20e30b12)

https://github.com/xerrors/Yuxi/commit/1e8b20e30b1258d1cd3ebf3af5c6212da4b84b48

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 59× 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.

Showing the most recent 100 of 154 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 54 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 19:21 UTCEG score recompute
  2. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-11-01 21:22 UTCEG score recompute
  4. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-10-31 23:30 UTCEG score recompute
  6. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-10-31 01:38 UTCEG score recompute
  8. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-30 03:46 UTCEG score recompute
  10. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-29 05:55 UTCEG score recompute
  12. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-28 08:03 UTCEG score recompute
  14. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-27 10:07 UTCEG score recompute
  16. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-26 12:14 UTCEG score recompute
  18. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-25 14:18 UTCEG score recompute
  20. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  21. 2026-10-23 20:27 UTCEG score recompute
  22. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-10-22 23:10 UTCEG score recompute
  24. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-22 01:19 UTCEG score recompute
Show 75 more
  1. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-10-21 03:22 UTCEG score recompute
  3. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  4. 2026-10-20 05:28 UTCEG score recompute
  5. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  6. 2026-10-19 06:57 UTCEG score recompute
  7. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-10-18 03:33 UTCEG score recompute
  9. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-10-17 10:49 UTCEG score recompute
  11. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-10-16 12:23 UTCEG score recompute
  13. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-15 14:08 UTCEG score recompute
  15. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-10-14 08:53 UTCEG score recompute
  17. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  18. 2026-10-13 05:09 UTCEG score recompute
  19. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-10-12 15:59 UTCEG score recompute
  21. 2026-10-11 19:42 UTCEG score recompute
  22. 2026-10-11 16:57 UTCEG score recompute
  23. 2026-10-11 14:20 UTCEG score recompute
  24. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  26. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  28. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  29. 2026-10-06 17:30 UTCEG score recompute
  30. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  31. 2026-10-05 19:10 UTCEG score recompute
  32. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  33. 2026-10-05 07:35 UTCEG score recompute
  34. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  35. 2026-10-03 20:15 UTCEG score recompute
  36. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  37. 2026-10-02 22:01 UTCEG score recompute
  38. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  39. 2026-10-02 08:22 UTCEG score recompute
  40. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  41. 2026-09-30 21:58 UTCEG score recompute
  42. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  43. 2026-09-29 04:51 UTCEG score recompute
  44. 2026-09-28 14:43 UTCEG score recompute
  45. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  46. 2026-09-27 16:54 UTCEG score recompute
  47. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  48. 2026-09-27 09:57 UTCEG score recompute
  49. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  50. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  51. 2026-09-25 03:43 UTCEG score recompute
  52. 2026-09-23 20:55 UTCEG score recompute
  53. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  54. 2026-09-22 21:07 UTCEG score recompute
  55. 2026-09-22 00:30 UTCEG score recompute
  56. 2026-09-20 20:54 UTCEG score recompute
  57. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  58. 2026-09-19 16:37 UTCEG score recompute
  59. 2026-09-18 22:12 UTCEG score recompute
  60. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  61. 2026-09-17 22:28 UTCEG score recompute
  62. 2026-09-17 00:23 UTCEG score recompute
  63. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  64. 2026-09-16 06:37 UTCEG score recompute
  65. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  66. 2026-09-15 06:55 UTCEG score recompute
  67. 2026-09-13 18:49 UTCEG score recompute
  68. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  69. 2026-09-12 17:05 UTCEG score recompute
  70. 2026-09-11 18:51 UTCEG score recompute
  71. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  72. 2026-09-11 10:14 UTCEG score recompute
  73. 2026-09-10 12:34 UTCEG score recompute
  74. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  75. 2026-09-09 05:18 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50561?
CVE-2026-50561 is a critical-severity vulnerability; its CVE record was published on August 12, 2026. Yuxi is a large-model-based intelligent knowledge base and knowledge graph agent development platform. Prior to version 0.6.2, the project's authentication mechanism contains a flaw. In affected versions, the system does not sufficiently validate the identity token in the Authorization header —…
When was the CVE record for CVE-2026-50561 published?
The CVE record for CVE-2026-50561 was published on August 12, 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 October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-50561 actively exploited?
CVE-2026-50561 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50561?
CVE-2026-50561 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50561?
A fix for CVE-2026-50561 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-50561

Explore →

Is Your Infrastructure Affected by CVE-2026-50561?

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

Book a Demo →Browse All CVEs