Description
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.
Published: 2026-08-12
Score: 9.4 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability arises because Yuxi versions before 0.6.2 accept any Administrator JWT in the Authorization header without validating the identity token’s issuer or instance. This weakness is a CWE‑287 Authentication Bypass. An attacker who obtains or constructs a valid token from another deployment can replay it against a different instance, directly bypassing login and acquiring full administrative privileges. Consequently, the attacker can modify configuration, create new admin accounts, or otherwise take total control of the backend interface.

Affected Systems

The flaw affects the Yuxi knowledge‑base platform prior to version 0.6.2. Only deployments of Yuxi that have not applied the 0.6.2 update are vulnerable. The CVE does not list other products; thus any instance running an affected release is at risk.

Risk and Exploitability

The CVSS score of 9.4 reflects the high impact and remote nature of the exploit. Because an attacker only needs to craft a valid JWT, the EPSS score is not published, but the vulnerability is broadly exploitable over the public network. It is not currently listed in the CISA KEV catalog, but the severity and ease of exploitation make immediate remediation critical. An attacker with network access can send an HTTP request containing the replayed token to the management API and gain full control of the instance.

Generated by OpenCVE AI on August 13, 2026 at 01:01 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Yuxi deployment to version 0.6.2 or later, which includes a complete fix for the token validation flaw.
  • If an upgrade is delayed, set the environment variable JWT_SECRET_KEY to a unique, robust value for each instance, ensuring tokens are generated with a different key per deployment.
  • Restrict access to backend management interfaces; avoid exposing them to the open internet or limit them to trusted networks.

Generated by OpenCVE AI on August 13, 2026 at 01:01 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 13 Aug 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Thu, 13 Aug 2026 10:15:00 +0000

Type Values Removed Values Added
First Time appeared Xerrors
Xerrors yuxi
Vendors & Products Xerrors
Xerrors yuxi

Wed, 12 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
Description 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.
Title Yuxi has a JWT Authentication Bypass Leading to Cross-Instance Administrator Token Reuse
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 9.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-13T16:19:19.494Z

Reserved: 2026-06-04T21:34:34.426Z

Link: CVE-2026-50561

cve-icon Vulnrichment

Updated: 2026-08-13T16:19:15.922Z

cve-icon NVD

Status : Received

Published: 2026-08-12T15:17:38.307

Modified: 2026-08-13T17:17:23.750

Link: CVE-2026-50561

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-13T09:48:36Z

Weaknesses