CVE-2026-61807

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: 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 IT asset/license management system. Prior to 8.6.2, a stored manufacturer or supplier name passed as the table component $name becomes data-selected-count-id in resources/views/partials/bootstrap-table.blade.php. Client-side code reads the browser-decoded countId, uses it as a selector, concatenates countId.substring(1) into an HTML string, and passes the string to jQuery .after(). A crafted name can therefore execute JavaScript when an authenticated user views the manufacturer detail page or supplier detail page, potentially exposing data or actions available to that session. This issue is fixed in version 8.6.2.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
28(Track)
EG Risk 28/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
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

August 19, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 19, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v8.6.2

Patch available: grokability/snipe-it v8.6.2

https://github.com/grokability/snipe-it/releases/tag/v8.6.2
github_commit Patch Available

commit d12ad3d53869 (grokability/snipe-it)

Patch available: grokability/snipe-it v8.6.2 (contains commit d12ad3d53869)

https://github.com/grokability/snipe-it/commit/d12ad3d53869443b96b663ba3ce2673ef343da71
github Patch Available

Stored DOM XSS via table selected-count IDs · Advisory · grokability/snipe-it · GitHub

https://github.com/grokability/snipe-it/security/advisories/GHSA-c8qc-wf67-342w

Vendor Advisories for CVE-2026-61807(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)
PackageVulnerable rangeFixed inDependents
snipe/snipe-it3.2.0 ... v8.6.1 (278 versions)8.6.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 48× 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-18 22:49 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 01:11 UTCEG score recompute
  4. 2026-09-17 03:34 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:56 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 08:19 UTCEG score recompute
  9. 2026-09-14 10:42 UTCEG score recompute
  10. 2026-09-12 15:28 UTCEG score recompute
  11. 2026-09-11 17:50 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 09:37 UTCEPSS rescore
  14. 2026-09-10 20:13 UTCEG score recompute
  15. 2026-09-09 02:34 UTCEG score recompute
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-07 19:41 UTCEG score recompute
  18. 2026-09-07 16:01 UTCEPSS rescore
  19. 2026-09-06 22:04 UTCEG score recompute
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-06 00:26 UTCEG score recompute
  22. 2026-09-05 02:48 UTCEG score recompute
  23. 2026-09-04 05:09 UTCEG score recompute
  24. 2026-09-04 05:07 UTCEPSS rescore
  25. 2026-09-03 07:10 UTCEG score recompute
Show 26 more
  1. 2026-09-02 14:12 UTCEPSS rescore
  2. 2026-09-02 09:32 UTCEG score recompute
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 11:50 UTCEG score recompute
  5. 2026-09-01 04:40 UTCEPSS rescore
  6. 2026-08-31 14:10 UTCEG score recompute
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 15:36 UTCEG score recompute
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-29 17:59 UTCEG score recompute
  11. 2026-08-28 21:42 UTCEPSS rescore
  12. 2026-08-26 23:39 UTCEG score recompute
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-26 02:02 UTCEG score recompute
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-25 04:24 UTCEG score recompute
  17. 2026-08-25 03:50 UTCEG score recompute
  18. 2026-08-23 09:47 UTCEG score recompute
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-22 12:10 UTCEG score recompute
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-21 14:33 UTCEG score recompute
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 19:19 UTCEG score recompute
  25. 2026-08-19 18:38 UTCEG score recompute
  26. 2026-08-19 18:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61807?
CVE-2026-61807 is a medium vulnerability published on August 19, 2026. Snipe-IT is an IT asset/license management system. Prior to 8.6.2, a stored manufacturer or supplier name passed as the table component $name becomes data-selected-count-id in resources/views/partials/bootstrap-table.blade.php. Client-side code reads the browser-decoded countId, uses it as a…
When was CVE-2026-61807 disclosed?
CVE-2026-61807 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61807 actively exploited?
CVE-2026-61807 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 78.8% of all scored CVEs.
What is the CVSS score of CVE-2026-61807?
CVE-2026-61807 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-61807?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61807, 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-61807

Explore →

Is Your Infrastructure Affected by CVE-2026-61807?

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

Start Free Scan →Browse All CVEs