/

CVE-2026-45730

Severity:

HIGH RISK

(8.3)

Authorization Bypass (CWE-862) in Nuclio Dashboard

CVE-2026-45730

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized Project Modification and Deletion

Severity:

HIGH RISK

(8.3)

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

A missing authorization check in Nuclio Dashboard's project management API allows an authenticated user to modify or delete projects they do not belong to. When a user can reach the affected write paths, project resources such as functions and API gateways may also be changed or removed.

Affected context

The vulnerability occurs in Nuclio Dashboard deployments using project management API write operations before version 1.16.0. The risk is present when an authenticated account can invoke the affected project update or deletion endpoints, while authorization decisions do not correctly verify membership or ownership of the targeted project.

Exploit preconditions

  • Attack surface: Nuclio Dashboard project management API
  • Required access: A valid authenticated Nuclio user account
  • Trigger point: Project update or deletion requests targeting a project outside the user's membership scope
  • Why exploitation is possible: Authorization enforcement does not consistently verify whether the authenticated user is permitted to modify the selected project

Why this happens

The underlying bug is an authorization enforcement failure mapped to CWE-862: Missing Authorization. The API applies authentication and may invoke policy checks, but the write paths do not reliably enforce project-level membership or ownership for the resource identified by the request. This creates an insecure direct operation pattern in which an authenticated identity can perform privileged actions against resources outside its authorized scope.

Potential impact

  • An attacker may modify projects they do not manage
  • An attacker could delete projects and associated functions
  • API gateways and other project resources may be altered or removed
  • Service availability may be disrupted
  • Unauthorized changes could cause data processing or event-routing failures

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every project management write operation rather than relying on authentication or client-side restrictions.

Common defensive patterns include:

  • Applying server-side, resource-level authorization checks to every project update and deletion request
  • Verifying project membership, ownership, and permitted roles against the target resource
  • Denying access by default when policy evaluation is missing, indeterminate, or inconsistent
  • Keeping authorization decisions close to the protected operation
  • Limiting project-management privileges through least-privilege roles
  • Using secure-by-default API behavior that does not expose cross-project operations
  • Recording and reviewing administrative project changes

How teams detect issues like this

Organizations commonly detect missing authorization through:

  • Static analysis and policy checks for endpoints that perform writes without corresponding authorization enforcement
  • Code review of resource identifiers, ownership checks, and policy evaluation on every mutation path
  • Authorization test matrices covering same-project, cross-project, administrator, and non-member identities
  • Dynamic testing that verifies denied users cannot update or delete resources outside their scope
  • Monitoring for unusual cross-project modification or deletion activity
  • API gateway or policy enforcement rules that require project-level authorization claims

Automated security review tools may help identify write endpoints whose authorization checks are absent, bypassable, or applied only on read paths.

Sources

SourceLink
github.comgithub.com/nuclio/nuclio/commit/1915cd26d514dcdd487517d4be56673fc02298e0
github.comgithub.com/nuclio/nuclio/pull/4107
github.comgithub.com/nuclio/nuclio/releases/tag/1.16.0
github.comgithub.com/nuclio/nuclio/security/advisories/GHSA-m8xg-8xg9-mxhm

Frequently asked

questions

It may be exploitable through the Nuclio Dashboard API when that API is reachable by an authenticated user and the affected authorization paths are enabled.

No. The described issue requires an authenticated account, but not membership in the target project. The account's ability to reach the API is the important prerequisite.

Enforce server-side, resource-level authorization on every project update and deletion operation, including explicit checks for project membership and role.

Use deny-by-default authorization, test every API mutation across privilege boundaries, and continuously review logs and policies for cross-resource access attempts.

Find out what's already
exploitable in your codebase.