CVE-2026-49870

mediumpriority · track · 0EPSS 0.004 · 35 %ileDEUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.40% (35th) EPSS
CVSS 5.9 · medium
Is it mine?
6 products
Check your exposure
Who says so?
3 sources
cert_bund · nvd · osv

EPSS · scored 2026-10-27

Snipe-IT is an IT asset/license management system. Prior to 8.6.1, POST /two-factor has no rate limiting, lockout, or attempt counter, allowing an attacker with valid credentials to submit unlimited TOTP guesses against the three accepted codes created by config/google2fa.php window=1. A successful guess creates a fully authenticated session. When two_factor_enabled is 1, POST /account/profile with two_factor_optin=0 can disable two-factor authentication without OTP reverification, while required mode 2 prevents that opt-out. An administrator can also use POST /api/v1/users/two_factor_reset to clear another user's secret. This issue is fixed in version 8.6.1.

01

cvss

Technical severity, 0–10. One row per scoring source.

5.9
010

base score 0–10 · higher = more severe · hover a vector to decode

v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:Nsecondary · security-advisories@github.comexploitability 1.6 · impact 4.2
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:Nsecondary · OSV
v3.15.4mediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N/E:Usecondary · CVSS-BT (t0sche)
02

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
03

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-770USCWE-770US
04

affected products (6)

Products and version ranges known to be affected.

05

advisories (2)

Vendor and ecosystem advisories describing this.

  • WID-SEC-W-2026-2051Snipe-IT: Mehrere Schwachstellen ermöglichen Umgehen von SicherheitsvorkehrungenDeutsch2026-06-23csaf · cert_bundDE

    Ein Angreifer kann mehrere Schwachstellen in Snipe-IT ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

  • GHSA-mr8g-2mj4-pcq2Snipe-IT's TOTP is Brute-Forceable Due to Missing Rate Limiting on `POST /two-factor`2026-06-23ghsa · osvUS

    ### 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

06

sources

Which sources assert this record, and when.

cert_bundnvdosvNVDCVE.orgMITRE
published 2026-08-19modified 2026-10-24
07

references (4) nvd

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan