CVE-2026-86746

MEDIUMPre-NVD 6.46.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-09. A secondary CVSS source baseline 6.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
6.4EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.4Exploit: No code on recordExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Snipe-IT before 8.7.0 contains an authorization bypass vulnerability in Livewire components that enforce authorization only at the route level, not within component lifecycle methods. Attackers with a valid authenticated session can replay signed component snapshots via POST /livewire/update to invoke protected methods and escalate privileges, including creating OAuth clients, minting personal access tokens, and accessing sensitive admin data.

CVSS v3
6.4
EG Score
6.4MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

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 (value × EchelonGraph’s weight)
Severity64% × 45%
The EG Score, 6.4 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 9, 2026

Last Modified

September 14, 2026

Advisory Details (2)

Auto-updated Sep 9, 2026
Fix referenced — no release confirmed yet. Sources: github.
Web page

Snipe-IT before 8.7.0 Authorization Bypass via Livewire Snapshot Replay | Advisories | VulnCheck

https://www.vulncheck.com/advisories/snipe-it-before-8.7.0-authorization-bypass-via-livewire-snapshot-replay
GitHub advisoryMentions a patch (unverified)

Livewire Component Authorization Bypass via `POST /livewire/update` Snapshot Replay · Advisory · grokability/snipe-it · GitHub

https://github.com/grokability/snipe-it/security/advisories/GHSA-jchx-hfqg-rm2m

Vendor Advisories for CVE-2026-86746(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 24× in last 7d / 82× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 94 are merged into the row they repeat.

  1. 2026-10-11 19:17 UTCEG score recompute
  2. 2026-10-11 16:33 UTCEG score recompute
  3. 2026-10-11 13:50 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-10-11 10:19 UTCEG score recompute
  6. 2026-10-11 10:19 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-10 08:47 UTCEG score recompute
  9. 2026-10-10 08:46 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-09 09:24 UTCEG score recompute
  12. 2026-10-09 09:24 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-08 09:18 UTCEG score recompute
  15. 2026-10-08 09:18 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-07 09:55 UTCEG score recompute
  18. 2026-10-07 09:55 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-10-06 10:32 UTCEG score recompute
  21. 2026-10-06 10:32 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  22. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-10-05 11:07 UTCEG score recompute
  24. 2026-10-05 11:07 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  25. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
Show 67 more
  1. 2026-10-04 11:40 UTCEG score recompute
  2. 2026-10-04 11:39 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  3. 2026-10-03 12:16 UTCEG score recompute
  4. 2026-10-03 12:16 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  5. 2026-10-02 12:53 UTCEG score recompute
  6. 2026-10-02 12:53 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  7. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-10-01 13:31 UTCEG score recompute
  9. 2026-10-01 13:31 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  10. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-09-30 14:09 UTCEG score recompute
  12. 2026-09-30 14:09 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  13. 2026-09-29 13:30 UTCEG score recompute
  14. 2026-09-29 13:30 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  15. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-09-28 13:49 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  17. 2026-09-27 14:26 UTCEG score recompute
  18. 2026-09-27 14:26 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  19. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-09-26 15:04 UTCEG score recompute
  22. 2026-09-26 15:04 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  23. 2026-09-25 15:22 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  24. 2026-09-24 15:58 UTCEG score recompute
  25. 2026-09-24 15:58 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  26. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  27. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  28. 2026-09-23 16:34 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  29. 2026-09-22 17:12 UTCEG score recompute
  30. 2026-09-22 17:12 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  31. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  32. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  33. 2026-09-21 17:46 UTCEG score recompute
  34. 2026-09-21 17:46 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  35. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  36. 2026-09-20 18:21 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  37. 2026-09-19 18:59 UTCEG score recompute
  38. 2026-09-19 18:59 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  39. 2026-09-18 19:37 UTCEG score recompute
  40. 2026-09-18 19:37 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  41. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  42. 2026-09-17 20:14 UTCEG score recompute
  43. 2026-09-17 20:14 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  44. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  45. 2026-09-16 19:27 UTCEG score recompute
  46. 2026-09-16 19:27 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  47. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  48. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  49. 2026-09-15 20:04 UTCEG score recompute
  50. 2026-09-15 20:04 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  51. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  52. 2026-09-14 20:41 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  53. 2026-09-14 18:16 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  54. 2026-09-13 18:14 UTCEG score recompute
  55. 2026-09-13 18:14 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  56. 2026-09-12 18:52 UTCEG score recompute
  57. 2026-09-12 18:52 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  58. 2026-09-11 19:29 UTCEG score recompute
  59. 2026-09-11 19:29 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  60. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  61. 2026-09-10 20:06 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  62. 2026-09-09 20:41 UTCEG score recompute
  63. 2026-09-09 20:41 UTCGHSA enrichmentGHSA-gqrx-3864-xfwx · GitHub severity HIGH · GitHub CVSS 6.4
  64. 2026-09-09 15:29 UTCEG score recompute
  65. 2026-09-09 14:27 UTCEG score recompute
  66. 2026-09-09 13:45 UTCEG score recomputeFirst assessed: 6.4 MEDIUM
  67. 2026-09-09 13:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86746?
CVE-2026-86746 is a medium-severity vulnerability; its CVE record was published on September 9, 2026. Snipe-IT before 8.7.0 contains an authorization bypass vulnerability in Livewire components that enforce authorization only at the route level, not within component lifecycle methods. Attackers with a valid authenticated session can replay signed component snapshots via POST /livewire/update to…
When was CVE-2026-86746 made public?
CVE-2026-86746 was made public on August 24, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 9, 2026. EchelonGraph's copy of the record carries a last-modified date of September 14, 2026; the record at its source may have been updated since.
Is CVE-2026-86746 actively exploited?
CVE-2026-86746 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86746?
CVE-2026-86746 has a CVSS base score of 6.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-86746?
A fix for CVE-2026-86746 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-86746 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-86746?

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