/

CVE-2026-75481

Severity:

HIGH RISK

(8.8)

Privilege Escalation (CWE-269) in SkyPilot Service Accounts

CVE-2026-75481

Deferred

Vulnerability type

Category:

Privilege Escalation

CWE:

CWE-269

Impact:

Administrative Account Takeover

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

SkyPilot does not adequately verify that an authenticated user is authorized to grant administrator roles when updating service account permissions. An attacker who can create or manage a service account may elevate it to administrator status and use its bearer token to control users and workspaces.

Affected context

The vulnerability occurs in SkyPilot deployments where authenticated users can create service accounts and update their permissions. Risk is elevated when authorization checks do not verify whether the requesting user is entitled to assign administrator roles, allowing a lower-privileged account to create an administrative service identity.

Exploit preconditions

  • Attack surface: SkyPilot service account management and permission-update functionality
  • Required access: Authenticated access sufficient to create or modify a service account
  • Trigger point: Updating service account permissions to include an administrator role
  • Why exploitation is possible: The authorization logic fails to confirm that the requesting user may grant administrator-level privileges
  • Follow-on access: A bearer token for the elevated service account can provide administrative access to users and workspaces

Why this happens

The underlying defect is an authorization failure in privilege assignment. SkyPilot validates that the request is authenticated but does not adequately enforce whether that principal is permitted to grant administrator roles. This maps to CWE-269: Improper Privilege Management, because a subject can obtain or assign privileges beyond those authorized by the intended security policy.

Potential impact

  • An attacker may obtain administrative control over SkyPilot users and workspaces
  • Unauthorized users could modify service accounts, permissions, or workspace resources
  • An attacker could disrupt workloads or alter platform configuration
  • Sensitive workspace data or credentials could be exposed
  • Administrative access could enable further compromise of connected infrastructure

General mitigation guidance

Mitigation generally focuses on enforcing authorization at every privilege-changing operation and reducing trust in caller-supplied role data.

Common defensive patterns include:

  • Require explicit authorization checks before assigning administrator or equivalent roles
  • Enforce server-side role and permission policies rather than trusting client-provided values
  • Separate service account creation from privileged role delegation
  • Apply least privilege and deny privilege expansion by default
  • Use narrowly scoped, short-lived bearer tokens where practical
  • Revalidate the actor's permissions when service account privileges are changed
  • Record and alert on administrator-role grants and service account token use

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review rules covering role-assignment endpoints and missing object-level authorization checks
  • Tests that attempt privilege changes using accounts with progressively limited permissions
  • Policy checks requiring server-side authorization for every administrator-role grant
  • Audit-log monitoring for unexpected service account creation, role elevation, or token use
  • Automated security testing that verifies users cannot grant privileges exceeding their own authority

Sources

SourceLink
github.comgithub.com/skypilot-org/skypilot
github.comgithub.com/skypilot-org/skypilot/blob/master/sky/users/server.py
github.comgithub.com/skypilot-org/skypilot/commit/8a3e00259cd374e662cd876c037164bcb070f78e
github.comgithub.com/skypilot-org/skypilot/issues/9846
vulncheck.comvulncheck.com/advisories/skypilot-authentication-bypass-via-service-account-role-escalation

Frequently asked

questions

It may be exploitable through SkyPilot's service account management interface when that interface is reachable by an authenticated attacker.

The attacker generally needs authenticated access that permits service account creation or permission updates. Anonymous access is not required by the described attack path.

Enforce server-side authorization that verifies the requesting principal is explicitly allowed to grant administrator roles before applying any permission change.

Use deny-by-default privilege policies, test horizontal and vertical authorization boundaries, constrain token privileges, and monitor all role and service account changes.

Find out what's already
exploitable in your codebase.