CVE-2026-49870: Snipe/snipe it Remote Code Execution Vulnerability

MODERATE
Advisory Identifier: GHSA-mr8g-2mj4-pcq2
Share
CVSS 5.9
CWE-770
Published
Advisory Summary

CVE-2026-49870 is a MODERATE (CVSS 5.9) remote code execution vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting Snipe/snipe it libraries in the Packagist ecosystem. The issue involves snipe-it's totp is brute-forceable due to missing rate limiting on `post /two-factor`. Remediation is available by upgrading affected packages to version 8.6.0.

CVE-2026-49870 at a Glance

CVE Identifier CVE-2026-49870
GHSA Identifier GHSA-mr8g-2mj4-pcq2
Severity MODERATE
CVSS v3.1 Base Score 5.9
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product Snipe/snipe it
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 5.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-49870

To remediate this vulnerability, upgrade all affected Snipe/snipe it dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

snipe/snipe-it fixed: 8.6.0 
Upgrade snipe/snipe-it to 8.6.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for snipe/snipe-it

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-49870, inspect your project dependencies for Snipe/snipe it:

inspect dependencies for snipe/snipe-it

Analyze the terminal output to locate any version of Snipe/snipe it in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 8.6.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In Snipe/snipe it, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact `POST /two-factor` had no rate limiting, lockout, or attempt counter. An attacker with valid credentials can submit unlimited TOTP guesses. The TOTP implementation accepts the current code plus one step on either side (`config/google2fa.php window=1`), so at any instant 3 of 1,000,000 codes are accepted. After a correct guess the attacker holds a fully authenticated session. If the instance is configured with 2FA in optional mode (`two_factor_enabled='1'`), the attacker can additionally disable 2FA via `POST /account/profile` with `two_factor_optin=0`. No OTP re-verification is required. The account is then accessible with the password alone on future logins. If 2FA is in required-for-all mode (`='2'`), the per-user opt-out path is closed and the impact stops at session-level account takeover. For an admin target, `POST /api/v1/users/two_factor_reset` additionally clears another user's 2FA secret. ### Patches Patched in v8.6.0

CVE-2026-49870 Affected Snipe/snipe it Versions

1 component(s)
Fixed Versions:
8.6.0
Product / Package Ecosystem Affected Versions Fixed Version
snipe/snipe-it
 Packagist
< 8.6.0
8.6.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/grokability/snipe-it/security/advisories/GHSA-mr8g-2mj4-pcq2
Snipe/snipe it Source Repository REPOSITORY
https://github.com/grokability/snipe-it

Frequently Asked Questions

What is CVE-2026-49870?
CVE-2026-49870 is a security vulnerability in Snipe/snipe it involving Snipe-IT's TOTP is Brute-Forceable Due to Missing Rate Limiting on `POST /two-factor` under CWE-770: Allocation of Resources Without Limits or Throttling.
Which Snipe/snipe it versions are affected?
Affected versions include releases prior to 8.6.0 across affected packages: snipe/snipe-it.
What version fixes CVE-2026-49870?
Upgrading to 8.6.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is snipe/snipe-it affected?
Yes, snipe/snipe-it is affected in releases prior to 8.6.0. Upgrade your dependency to 8.6.0 or later.
What is the CVSS score of CVE-2026-49870?
CVE-2026-49870 has a CVSS v3.1 base score of 5.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N.
What CWE is associated with CVE-2026-49870?
CVE-2026-49870 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check Packagist dependencies for CVE-2026-49870?
Run the dependency tree command: 'inspect dependencies for snipe/snipe-it'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mr8g-2mj4-pcq2",
  "modified" : "2026-06-23T22:32:04Z",
  "published" : "2026-06-23T22:32:04Z",
  "aliases" : [ "CVE-2026-49870" ],
  "summary" : "Snipe-IT's TOTP is Brute-Forceable Due to Missing Rate Limiting on `POST /two-factor`",
  "details" : "### Impact\n`POST /two-factor` had no rate limiting, lockout, or attempt counter. An attacker with valid credentials can submit unlimited TOTP guesses. The TOTP implementation accepts the current code plus one step on either side (`config/google2fa.php window=1`), so at any instant 3 of 1,000,000 codes are accepted.\n\nAfter a correct guess the attacker holds a fully authenticated session. If the instance is configured with 2FA in optional mode (`two_factor_enabled='1'`), the attacker can additionally disable 2FA via `POST /account/profile` with `two_factor_optin=0`. No OTP re-verification is required. The account is then accessible with the password alone on future logins. If 2FA is in required-for-all mode (`='2'`), the per-user opt-out path is closed and the impact stops at session-level account takeover. For an admin target, `POST /api/v1/users/two_factor_reset` additionally clears another user's 2FA secret.\n\n### Patches\nPatched in v8.6.0",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "snipe/snipe-it"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.6.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/grokability/snipe-it/security/advisories/GHSA-mr8g-2mj4-pcq2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/grokability/snipe-it"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-23T22:32:04Z",
    "nvd_published_at" : null
  }
}