Is CVE-2026-63493 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-63493 being exploited in the wild.

How severe is CVE-2026-63493?

High severity, with a CVSS score of 4, published 24 September 2026.

Which products and versions are affected?

snipe/snipe-it (Packagist) < 8.7.0, ECOSYSTEM:introduced=0,fixed=8.7.0.

Is there a fix for CVE-2026-63493?

Yes. snipe/snipe-it (Packagist): upgrade to 8.7.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-63493 attacked?

It is attacked over the network.

Am I affected by CVE-2026-63493?

Check whether you run snipe/snipe-it (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63493: Snipe-IT 2FA bypass via API token flow

Q: Is there a fix for CVE-2026-63493?

Yes. snipe/snipe-it (Packagist): upgrade to 8.7.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-63493 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-63493?

Check whether you run snipe/snipe-it (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-63493 · Severity: high · CVSS 4 · Published 2026-09-24

Snipe-IT is an IT asset management system that allows teams to track hardware, software, and other resources across an organization. An attacker who knows a user's password can completely bypass that user's two-factor authentication (2FA) by obtaining a long-lived API token with full read/write access. If the compromised account is an admin, the attacker can also disable 2FA protection, lock the legitimate user out, and take over the account's web access.

Technologies: snipe/snipe-it (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-63493 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-63493 being exploited in the wild.
How severe is CVE-2026-63493?: High severity, with a CVSS score of 4, published 24 September 2026.
Which products and versions are affected?: snipe/snipe-it (Packagist) < 8.7.0, ECOSYSTEM:introduced=0,fixed=8.7.0.
Is there a fix for CVE-2026-63493?: Yes. snipe/snipe-it (Packagist): upgrade to 8.7.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-63493 attacked?: It is attacked over the network.
Am I affected by CVE-2026-63493?: Check whether you run snipe/snipe-it (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

snipe/snipe-it (Packagist): upgrade to 8.7.0 or later
```
composer require snipe/snipe-it:^8.7.0
```

Technical details

The vulnerability stems from inconsistent 2FA enforcement: the CheckForTwoFactor middleware is registered only on the web middleware group, not the API group. After a user authenticates with a correct password, they can access the /two-factor endpoint (which is explicitly exempted from 2FA checks) to obtain a Passport API token cookie, then use the unauthenticated API group to mint a persistent personal access token via /api/v1/account/personal-access-tokens. This token grants full API access without ever requiring the second factor, and since the API endpoint is gated only by a permission check (not 2FA validation), any user with the self.api permission can generate tokens. The exploit requires only knowledge of the target's password; no user interaction or additional authentication is needed. The fix adds EnforceApiTwoFactorEnrollment middleware to the API group to verify 2FA enrollment status before issuing or accepting API tokens.

Affected products

Snipe-IT Snipe-IT prior to commit 87c362962a

Identifiers

CVE-2026-63493
GHSA-hxcx-9h4f-42xx

Timeline

2026-09-24: disclosed: Advisory published
2026-09-24: patched: Fixed via commit 87c362962a and PR #19294

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.