Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-50561 – Authentication Bypass (JWT Cross-Instance Token Reuse) – Yuxi < 0.6.2

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-50561 is a critical authentication bypass vulnerability in Yuxi, a large-model-based intelligent knowledge base platform maintained by xerrors, affecting all versions prior to 0.6.2. The flaw stems from insufficient validation of identity tokens presented in the Authorization header, allowing administrator tokens from one deployment or test instance to be reused to gain unauthorized access on a different instance. The issue carries a CVSS v3.1 base score of 9.4 (Critical) and requires no authentication or user interaction to exploit remotely.

Technical details

  • Root cause: Yuxi’s authentication mechanism only performs a validity check on JWT identity tokens submitted in the Authorization header, without sufficiently validating that the token belongs to the specific deployment instance being accessed.
  • Trigger conditions: An attacker possesses or obtains an administrator token issued by any Yuxi deployment (e.g., a test/staging environment) and submits it to a different, target Yuxi instance.
  • Attack vector: Network — the malicious token is sent directly to the exposed backend management interface; no prior authentication or victim interaction is required.
  • Impact: Successful exploitation bypasses login entirely, granting administrator privileges that allow access to system configuration, invocation of backend APIs, creation of additional admin accounts, and full compromise of the application backend.

Affected software

  • Yuxi (xerrors/Yuxi): all versions prior to 0.6.2

Severity

  • CVSS v3.1 Base Score: 9.4 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Mitigation and recommended actions

  • Immediate: Upgrade to Yuxi version 0.6.2 or later, which fixes the token validation flaw.
  • If immediate patching is not possible:
    • Set the JWT_SECRET_KEY environment variable to a unique, strong, deployment-specific value rather than relying on defaults or shared secrets.
    • Restrict network exposure of the Yuxi backend/administrative management interface so it is not reachable from the public internet.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge