CVE-2026-49870 is a medium-severity allocation of resources without limits or throttling vulnerability in snipe/snipe-it (composer), affecting versions < 8.6.0. It is fixed in 8.6.0.
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 (twofactorenabled='1'), the attacker can additionally disable 2FA via POST /account/profile with twofactoroptin=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/twofactorreset additionally clears another user's 2FA secret. Patches Patched in v8.6.0
The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.
CVE-2026-49870 has a CVSS score of 5.9 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (8.6.0). Upgrading removes the vulnerable code path.
composer
snipe/snipe-it (< 8.6.0)snipe/snipe-it → 8.6.0 (composer)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-49870 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-49870 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-49870 in your environment →Upgrade snipe/snipe-it to 8.6.0 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-49870 is a medium-severity allocation of resources without limits or throttling vulnerability in snipe/snipe-it (composer), affecting versions < 8.6.0. It is fixed in 8.6.0. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
CVE-2026-49870 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
snipe/snipe-it (composer) versions < 8.6.0 is affected.
Yes. CVE-2026-49870 is fixed in 8.6.0. Upgrade to this version or later.
Whether CVE-2026-49870 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade snipe/snipe-it to 8.6.0 or later.