/

CVE-2026-92780

Severity:

HIGH RISK

(8.8)

Missing Authorization (CWE-862) in KnowStreaming APIs

CVE-2026-92780

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Privilege Escalation and Unauthorized Administrative Access

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

KnowStreaming through version 3.4.1 does not consistently enforce role-based authorization on protected REST API endpoints. An authenticated user may access identity-management functions to create administrator accounts or grant administrative privileges without having the required role.

Affected context

The vulnerability occurs in KnowStreaming deployments where authenticated REST API users can reach identity-management or other protected endpoints without effective server-side role checks. Risk depends on the exposed API surface, the permissions assigned to authenticated accounts, and whether administrative operations are accessible through the affected request paths.

Exploit preconditions

  • Attack surface: KnowStreaming REST API endpoints - Required access: A valid authenticated user account - Trigger point: Identity-management requests that create accounts or modify privileges - Why exploitation is possible: The server does not reliably verify that the

authenticated principal has the role required for the requested administrative action

Why this happens

The underlying issue is missing authorization enforcement, mapped to CWE-862. Authentication establishes that a requester has an identity, but the affected endpoints fail to perform a corresponding server-side permission check before executing privileged operations. This insecure pattern treats authenticated access as sufficient for authorization-sensitive functionality.

Potential impact

  • An authenticated user may create unauthorized administrator accounts
  • An attacker could grant an existing account administrative privileges
  • Administrative control over KnowStreaming could be obtained
  • Sensitive configuration or operational data may be accessed or modified
  • The platform could be used to affect connected streaming infrastructure

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every protected server-side operation rather than relying on authentication or client-side controls. Common defensive patterns include explicit role and permission checks for identity-management actions, deny-by-default endpoint policies, centralized authorization middleware, and consistent handling of direct API calls. Access should be limited to the minimum privileges required, administrative functions should use separate high-privilege roles, and trust in client-supplied role indicators should be reduced. Audit logging and review of privilege changes can help contain and investigate unauthorized activity.

How teams detect issues like this

Detection approaches include static analysis and code review for REST handlers that perform identity or privilege changes without authorization middleware or explicit permission checks. Reviewers can compare endpoint inventories against role policies, test direct API access with lower-privileged accounts, and monitor logs for unexpected account creation or role changes. Policy enforcement can require authorization annotations, centralized guards, and negative access tests for administrative routes; automated application security review tools may help identify inconsistent enforcement.

Sources

SourceLink
github.comgithub.com/didi/KnowStreaming
github.comgithub.com/didi/KnowStreaming/blob/v3.4.0/km-rest/src/main/java/com/xiaojukeji/know/streaming/km/rest/interceptor/PermissionInterceptor.java#L46-L74
github.comgithub.com/didi/KnowStreaming/issues/1263
vulncheck.comvulncheck.com/advisories/knowstreaming-through-3.4.1-missing-authorization-on-the-rest-api

Frequently asked

questions

An attacker generally needs a valid authenticated KnowStreaming account, but

the account may not need administrative privileges.

No. Authentication confirms the user's identity, while the affected endpoints

must separately verify whether that user is authorized to perform each action.

Enforce centralized, server-side, deny-by-default authorization checks on every

administrative and identity-management endpoint.

Maintain an explicit endpoint-to-permission policy, test access with accounts

having different roles, monitor privilege changes, and prevent client-supplied

identity or role data from determining authorization.

Find out what's already
exploitable in your codebase.