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.
CVE-2026-49870
MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(medium)
- EG Risk
- 27(Track)EG Risk 27/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity59% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
June 23, 2026
Last Modified
August 21, 2026
Advisory Details (4)
Auto-updated Aug 19, 2026Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available
TOTP Brute-Forceable Due to Missing Rate Limiting on `POST /two-factor` · Advisory · grokability/snipe-it · GitHub
Affected: v8.6.0
https://github.com/grokability/snipe-it/security/advisories/GHSA-mr8g-2mj4-pcq2github_release Patch Available
v8.6.1
Patch available: grokability/snipe-it v8.6.1
https://github.com/grokability/snipe-it/releases/tag/v8.6.1github_pr Patch Available
Misc security fixes
Patch available: grokability/snipe-it v8.6.1 (PR #19072 merged 2026-05-26)
https://github.com/grokability/snipe-it/pull/19072github_commit Patch Available
commit 46d5234fd73d (grokability/snipe-it)
Patch available: grokability/snipe-it v8.6.1 (contains commit 46d5234fd73d)
https://github.com/grokability/snipe-it/commit/46d5234fd73d5fb928af43eb67d3bf7643d53115Vendor Advisories for CVE-2026-49870(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| snipe/snipe-it | 3.2.0 ... v8.5.0 (276 versions) | 8.6.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 01:32 UTCEG score recompute
- 2026-08-24 00:31 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 23:30 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 22:27 UTCEG score recompute
- 2026-08-21 22:01 UTCEG score recompute
- 2026-08-21 21:23 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 19:21 UTCEG score recompute
- 2026-07-31 03:37 UTCEG score recompute
- 2026-07-26 15:51 UTCEG score recompute
- 2026-07-23 03:18 UTCEG score recompute
- 2026-06-23 23:31 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-770
Frequently asked(5)
What is CVE-2026-49870?
CVE-2026-49870 is a medium vulnerability published on June 23, 2026. 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…
When was CVE-2026-49870 disclosed?
CVE-2026-49870 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49870 actively exploited?
CVE-2026-49870 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.5% of all scored CVEs.
What is the CVSS score of CVE-2026-49870?
CVE-2026-49870 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-49870?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49870, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49870
Is Your Infrastructure Affected by CVE-2026-49870?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.