{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-50561 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-50561 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-50561 is a critical authentication bypass vulnerability in xerrors Yuxi, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-50561 and fix it if it is affected.\n\nWhat it is: CVE-2026-50561 is a critical authentication bypass vulnerability in xerrors Yuxi, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-50561 in the wild and no public exploit code.\n\nAffected product: xerrors Yuxi. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-50561/ (Markdown: https://insights.sbomify.com/CVE-2026-50561/index.md)","id":"CVE-2026-50561","markdown":"https://insights.sbomify.com/CVE-2026-50561/index.md","name":"CVE-2026-50561","record":{"aliases":["GHSA-6959-99pq-c56x"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"AI knowledge base platform","requires_auth":"none","summary":"Attackers can reuse admin tokens from other instances to bypass authentication and take over the Yuxi knowledge base backend.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Yuxi has a JWT Authentication Bypass Leading to Cross-Instance Administrator Token Reuse","id":"CVE-2026-50561","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"FastGPT: Untrusted PR artifacts are pushed and deployed by privileged preview workflows","id":"CVE-2026-50562"},"packages":[],"prev":{"headline":"Netty susceptible to HTTP/2 Reset Attack with different on-the-wire signature","id":"CVE-2026-50560"},"products":["Yuxi"],"published":"2026-08-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["xerrors"]},"summary":"Attackers can reuse admin tokens from other instances to bypass authentication and take over the Yuxi knowledge base backend.","url":"https://insights.sbomify.com/CVE-2026-50561/"}