Bisheng SSO Issues Admin Tokens Without Checking the Caller

CERT/CC disclosed three Bisheng access-control flaws on October 14. The legacy POST /user/sso endpoint can issue a JWT for a supplied username without authenticating the caller. It can also register a missing name; a new account matching the configured administrator or created as the first user gets super-administrator rights. This SSO flaw, CVE-2026-96679, remains unpatched. DataElement/Bisheng did not respond to CERT/CC’s coordination efforts.

Identify Bisheng installations and check the installed release, whether BISHENGPRO=true is set, and who can reach POST /user/sso through every proxy and ingress. Disable the legacy route or enforce JWT validation; if an integration still needs it, restrict access to a trusted local or same-origin path. From outside that approved path, a request must be denied or the route disabled; an authorized authentication test must yield no JWT for an unauthenticated caller. Review prior POST /user/sso requests alongside account activity; CERT/CC provides no request fingerprint for distinguishing attacks from integration traffic.

Separately, the authenticated cross-user assistant flaw CVE-2026-100156 was fixed in 2.5.0; it can charge inference to another user’s provider account and expose tools and workflows. The workflow-version read flaw CVE-2026-96681 was fixed in 3.0.0. Verify those release floors on the running service while restricting the still-unpatched SSO endpoint.