/

CVE-2026-86762

Severity:

HIGH RISK

(8.1)

Broken Access Control (CWE-862) in Snipe-IT REST API

CVE-2026-86762

Analyzed

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-862

Impact:

Unauthorized API access and privilege retention

Severity:

HIGH RISK

(8.1)

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

Snipe-IT does not consistently enforce account deactivation across its API authentication path. An existing Passport personal access token may continue to provide REST API access at the user's previous permission level until it expires, potentially allowing a deactivated account to read or modify organizational data.

Affected context

The issue occurs in Snipe-IT deployments where the API middleware group does not apply account-activation checks and deactivation does not invalidate previously issued Passport personal access tokens. Web login may correctly reject the deactivated account while API requests authenticated with an existing token continue to be processed. The risk is greatest when the account has write access or user-management privileges.

Exploit preconditions

  • Attack surface: Snipe-IT REST API endpoints
  • Required access: A valid API personal access token issued to an account before deactivation
  • Trigger point: Authentication of API requests after the associated account has been deactivated
  • Why exploitation is possible: API authentication can accept an unexpired token without applying the account-status check or revoking tokens associated with the deactivated account
  • Additional condition for self-reactivation: The retained token must have permission to manage users or otherwise change account activation state

Why this happens

The vulnerability results from inconsistent authorization enforcement between web and API request paths. Account deactivation is checked during web login, but the API middleware group does not apply the equivalent activation-state check, and existing Passport tokens remain valid after deactivation. This represents CWE-862: Missing Authorization, because the application fails to enforce a required authorization condition—the account's active status—before granting access to protected API resources.

Potential impact

  • A deactivated account may continue reading assets, users, licenses, and other API-accessible data.
  • The account may retain its previous write permissions and modify application records.
  • Sensitive organizational information could be exposed or altered.
  • A user with sufficient privileges could reactivate the deactivated account through the API.
  • An attacker controlling the token could maintain access until token expiration or other token invalidation occurs.

General mitigation guidance

Mitigation generally focuses on making account-status enforcement consistent across every authentication path and treating deactivation as a token-revocation event.

Common defensive patterns include:

  • Applying active-account checks to all API authentication and authorization flows.
  • Revoking or invalidating all personal access tokens when an account is deactivated.
  • Evaluating token validity against current account state rather than relying only on token expiration.
  • Using short-lived access tokens with controlled renewal and centralized revocation.
  • Applying least privilege to API tokens, especially for user-management operations.
  • Separating account deactivation authority from ordinary user-management permissions where practical.
  • Requiring server-side authorization checks for sensitive state changes, including account reactivation.

How teams detect issues like this

Detection approaches can include:

  • Static analysis and code review checks confirming that API middleware enforces current account status.
  • Tests that deactivate an account and verify that previously issued tokens cannot access protected endpoints.
  • Tests covering token revocation, refresh, expiration, and reactivation-related authorization boundaries.
  • Monitoring for API requests made with tokens belonging to deactivated accounts.
  • Alerting on attempts to reactivate accounts or change privilege state through API calls.
  • Policy enforcement requiring centralized authorization middleware for all protected API routes.

Automated security review tools may help identify middleware-group inconsistencies and missing authorization checks.

Sources

SourceLink
github.comgithub.com/grokability/snipe-it/commit/b3f12f974bb2c0175ea68dad163ed04726db4280
github.comgithub.com/grokability/snipe-it/security/advisories/GHSA-cj4w-vx6j-42rf
vulncheck.comvulncheck.com/advisories/snipe-it-before-8.7.0-authentication-bypass-via-api-middleware

Frequently asked

questions

Yes, where the Snipe-IT REST API is reachable and an attacker possesses an unexpired personal access token belonging to a deactivated account.

No. The relevant condition is possession of an existing valid API token; web-login denial does not necessarily invalidate that token.

Enforce account-status checks on every API request and revoke all active personal access tokens when an account is deactivated.

Test deactivation across web, API, token-refresh, and background request paths, while applying least privilege and centralized authorization policies to token-based access.

Find out what's already
exploitable in your codebase.