CVE-2026-86747

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-09-09. a secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Snipe-IT is an open source IT asset management system. In versions up to and including 8.6.3, the report acceptance endpoints POST /reports/unaccepted_assets/sent_reminder (ReportsController::sentAssetAcceptanceReminder) and DELETE /reports/unaccepted_assets/{acceptanceId}/delete (ReportsController::deleteAssetAcceptance) are not correctly scoped when Full Multiple Company Support (FMCS) is enabled. In 8.6.3 the guard ReportsController::currentUserCanAccessAcceptance() early-exits with 'return true' when '! $user->company_id' is truthy, which is the case for every pivot-only user (a user associated with companies through the company_user pivot table whose scalar users.company_id column is NULL); versions prior to 8.6.3 lacked the guard altogether. As a result, an authenticated user holding the reports.view permission can send acceptance-reminder emails for, and permanently delete, any pending acceptance record in the install regardless of which company owns the underlying checkoutable. Deletion is destructive and forfeits the acceptance audit trail for the affected item, and the reminder email exposes limited cross-company acceptance context (item name and assignment metadata) to the recipient. Acceptance IDs are sequential integers and can be enumerated. This issue is fixed in version 8.7.0.

CVSS v3
5.4
EG Score
5.4(high)
EG Risk
24(Track)
EG Risk 24/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 computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 14, 2026

Advisory Details (2)

Auto-updated Sep 9, 2026
Patch available. Sources: github.
generic Patch Available

snipe-it before 8.7.0 Authorization Bypass via Pivot-Only User | Advisories | VulnCheck

https://www.vulncheck.com/advisories/snipe-it-before-8.7.0-authorization-bypass-via-pivot-only-user
github Patch Available

Reports: Pivot-Only User Bypasses FMCS Scope on Acceptance Reminder and Delete Endpoints · Advisory · grokability/snipe-it · GitHub

https://github.com/grokability/snipe-it/security/advisories/GHSA-p5wx-p3vv-g6p2

Vendor Advisories for CVE-2026-86747(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 50× 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.

  1. 2026-09-24 21:47 UTCEG score recompute
  2. 2026-09-24 21:47 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-23 21:08 UTCEG score recompute
  5. 2026-09-23 21:08 UTCGHSA enrichment
  6. 2026-09-23 17:54 UTCEPSS rescore
  7. 2026-09-22 21:11 UTCEG score recompute
  8. 2026-09-22 21:11 UTCGHSA enrichment
  9. 2026-09-22 16:01 UTCEPSS rescore
  10. 2026-09-21 21:13 UTCEG score recompute
  11. 2026-09-21 21:13 UTCGHSA enrichment
  12. 2026-09-21 21:09 UTCEPSS rescore
  13. 2026-09-20 21:16 UTCEG score recompute
  14. 2026-09-20 21:16 UTCGHSA enrichment
  15. 2026-09-20 20:16 UTCEPSS rescore
  16. 2026-09-19 21:18 UTCEG score recompute
  17. 2026-09-19 21:18 UTCGHSA enrichment
  18. 2026-09-18 21:20 UTCEG score recompute
  19. 2026-09-18 21:20 UTCGHSA enrichment
  20. 2026-09-18 19:28 UTCEPSS rescore
  21. 2026-09-17 21:12 UTCEG score recompute
  22. 2026-09-17 21:12 UTCGHSA enrichment
  23. 2026-09-17 19:32 UTCEPSS rescore
  24. 2026-09-16 21:14 UTCEG score recompute
  25. 2026-09-16 21:14 UTCGHSA enrichment
Show 25 more
  1. 2026-09-16 14:09 UTCEPSS rescore
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-15 20:50 UTCEG score recompute
  4. 2026-09-15 20:50 UTCGHSA enrichment
  5. 2026-09-15 03:12 UTCEPSS rescore
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-14 20:35 UTCGHSA enrichment
  8. 2026-09-14 15:14 UTCEG score recompute
  9. 2026-09-14 15:14 UTCGHSA enrichment
  10. 2026-09-13 15:16 UTCGHSA enrichment
  11. 2026-09-12 15:17 UTCEG score recompute
  12. 2026-09-12 15:17 UTCGHSA enrichment
  13. 2026-09-11 15:20 UTCEG score recompute
  14. 2026-09-11 15:20 UTCGHSA enrichment
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-10 15:22 UTCEG score recompute
  18. 2026-09-10 15:22 UTCGHSA enrichment
  19. 2026-09-10 15:00 UTCEG score recompute
  20. 2026-09-10 15:00 UTCGHSA enrichment
  21. 2026-09-09 20:41 UTCEG score recompute
  22. 2026-09-09 20:41 UTCGHSA enrichment
  23. 2026-09-09 14:26 UTCEG score recompute
  24. 2026-09-09 13:45 UTCEG score recompute
  25. 2026-09-09 13:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-86747?
CVE-2026-86747 is a medium vulnerability published on September 9, 2026. Snipe-IT is an open source IT asset management system. In versions up to and including 8.6.3, the report acceptance endpoints POST /reports/unacceptedassets/sentreminder (ReportsController::sentAssetAcceptanceReminder) and DELETE /reports/unacceptedassets/{acceptanceId}/delete…
When was CVE-2026-86747 disclosed?
CVE-2026-86747 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86747 actively exploited?
CVE-2026-86747 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 85.5% of all scored CVEs.
What is the CVSS score of CVE-2026-86747?
CVE-2026-86747 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-86747?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86747, 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

Explore the affected products and dependency analysis for CVE-2026-86747

Explore →

Is Your Infrastructure Affected by CVE-2026-86747?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs