CERT/CC Warns of Three Bisheng Authorization Vulnerabilities
Tech GuruQuick Answer
CERT/CC published VU#166125 for DataElement Bisheng legacy SSO, workflow APIs, and assistant service. CERT/CC documented pre-authentication account takeover, cross-user workflow disclosure, and cross-user LLM credential abuse; one authentication-bypass path remained unpatched at publication. Match the exact preconditions, follow the record-specific remediation, validate affected workflows, and retain evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory Bisheng versions, legacy SSO exposure, role assignments, workflow APIs, assistants, tools, and provider credentials; deploy 2.5.0 or 3.0.0 where applicable; restrict POST /user/sso; rotate exposed credentials; and review cross-user access.
Last verified: 2026-10-15 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | DataElement Bisheng legacy SSO, workflow APIs, and assistant service |
|---|---|
| Advisory | VU#166125 |
| CVEs | CVE-2026-100156, CVE-2026-96679, CVE-2026-96681 |
| Authoritative release date | 2026-10-14 00:00:00 UTC |
| Authority revision date | 2026-10-14 00:00:00 UTC |
| Affected versions | Bisheng deployments with the legacy POST /user/sso path, cross-user workflow access, or assistant-service versions before 2.5.0 as detailed in VU#166125. |
| Fixed version | Bisheng 2.5.0 for CVE-2026-100156; 3.0.0 for CVE-2026-96681; restrict or disable the legacy SSO endpoint for the unpatched CVE-2026-96679 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
CERT/CC documented pre-authentication account takeover, cross-user workflow disclosure, and cross-user LLM credential abuse; one authentication-bypass path remained unpatched at publication.
What To Validate Now
- Inventory. Locate DataElement Bisheng legacy SSO, workflow APIs, and assistant service deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: Bisheng deployments with the legacy POST /user/sso path, cross-user workflow access, or assistant-service versions before 2.5.0 as detailed in VU#166125. Do not infer applicability from product family or severity alone.
- Remediate. Apply Bisheng 2.5.0 for CVE-2026-100156; 3.0.0 for CVE-2026-96681; restrict or disable the legacy SSO endpoint for the unpatched CVE-2026-96679 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
CVE-2026-96679 had no vendor fix when CERT/CC published. Treat the endpoint restriction as a compensating control, validate it at every proxy and origin, and track supported remediation. Preserve the authority snapshot, asset and owner records, before-and-after versions, change approval, installation output, validation results, exceptions, and rollback evidence.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
