CVE-2026-62368

HIGHNVD 8.48.4
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.4 under NVD CVSS v3. EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-09-24) is not newer than that change (2026-09-29), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-86292 (ENISA EUVD) · GHSA-p9h3-gvpq-5539 (GitHub Security Advisories)Source: ENISA EUVD

8.4EG
EchelonGraph verdictPlan a fixRemediate 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.4%CVSS: 8.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Snipe-IT is an IT asset/license management system. Prior to 8.7.0, a user with the customfields.create permission can store markup in CustomField.name, and app/Presenters/AssetPresenter.php assigns that value as an unescaped bootstrap-table header title. When another user opens an asset-list page associated with the fieldset, the stored markup executes on page load in that user's Snipe-IT session. This can expose same-origin data and perform authenticated actions with the victim's privileges, including privilege escalation when a superuser views the affected list. This issue is fixed in version 8.7.0.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
54
EG Risk 54/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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 available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

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.

The score's inputs: 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 24, 2026

Last Modified

September 29, 2026

Advisory Details (3)

Auto-updated Sep 24, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub release Patch Available

v8.7.0

Patch available: grokability/snipe-it v8.7.0

https://github.com/grokability/snipe-it/releases/tag/v8.7.0
GitHub commit Patch Available

commit 58754e4e3b86 (grokability/snipe-it)

Patch available: grokability/snipe-it v8.7.0 (contains commit 58754e4e3b86)

https://github.com/grokability/snipe-it/commit/58754e4e3b86b58a0c4523012ef04a2ae990d2c8
GitHub advisoryMentions a patch (unverified)

Stored XSS via Custom Field name in asset-list column headers · Advisory · grokability/snipe-it · GitHub

https://github.com/grokability/snipe-it/security/advisories/GHSA-p9h3-gvpq-5539

Vendor Advisories for CVE-2026-62368(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composersnipe/snipe-it @ 8.7.0 (fixes < 8.7.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
snipe/snipe-it3.2.0 ... v8.6.3 (280 versions)
  • every version up to 8.7.0: fixed in 8.7.0
—

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  3. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-p9h3-gvpq-5539 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-11-01 07:41 UTCEG score recompute
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-28 23:03 UTCEG score recompute
  9. 2026-10-28 21:55 UTCOSV refresh
  10. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-25 14:14 UTCEG score recompute
  15. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-10-21 02:44 UTCEG score recompute
  20. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  22. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-10-18 03:24 UTCEG score recompute
  24. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
Show 46 more
  1. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  4. 2026-10-13 12:54 UTCEG score recompute
  5. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  6. 2026-10-12 15:49 UTCEG score recompute
  7. 2026-10-11 19:34 UTCEG score recompute
  8. 2026-10-11 16:49 UTCEG score recompute
  9. 2026-10-11 14:11 UTCEG score recompute
  10. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  11. 2026-10-11 12:54 UTCEG score recompute
  12. 2026-10-11 01:27 UTCEG score recompute
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  14. 2026-10-10 02:31 UTCEG score recompute
  15. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  16. 2026-10-09 04:13 UTCEG score recompute
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  18. 2026-10-08 02:05 UTCEG score recompute
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  20. 2026-10-06 16:37 UTCEG score recompute
  21. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  22. 2026-10-05 18:15 UTCEG score recompute
  23. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  24. 2026-10-05 07:03 UTCEG score recompute
  25. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  26. 2026-10-03 21:33 UTCEG score recompute
  27. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  28. 2026-10-02 23:15 UTCEG score recompute
  29. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  30. 2026-10-02 00:49 UTCEG score recompute
  31. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  32. 2026-09-30 15:18 UTCEG score recompute
  33. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  34. 2026-09-29 16:55 UTCEG score recompute▲ 0.30
  35. 2026-09-29 16:54 UTCNVD updateCVSS v3 → 8.4
  36. 2026-09-29 06:58 UTCEG score recompute
  37. 2026-09-28 19:49 UTCEG score recompute
  38. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  39. 2026-09-27 21:30 UTCEG score recompute
  40. 2026-09-26 23:09 UTCEG score recompute
  41. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  42. 2026-09-26 00:48 UTCEG score recompute
  43. 2026-09-24 18:35 UTCEG score recompute
  44. 2026-09-24 17:18 UTCEG score recompute
  45. 2026-09-24 16:47 UTCEG score recomputeFirst assessed: 8.1 HIGH
  46. 2026-09-24 16:46 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-62368?
CVE-2026-62368 is a high-severity vulnerability; its CVE record was published on September 24, 2026. Snipe-IT is an IT asset/license management system. Prior to 8.7.0, a user with the customfields.create permission can store markup in CustomField.name, and app/Presenters/AssetPresenter.php assigns that value as an unescaped bootstrap-table header title. When another user opens an asset-list page…
When was the CVE record for CVE-2026-62368 published?
The CVE record for CVE-2026-62368 was published on September 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 29, 2026; the record at its source may have been updated since.
Is CVE-2026-62368 actively exploited?
CVE-2026-62368 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62368?
CVE-2026-62368 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-62368?
A fix for CVE-2026-62368 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62368 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62368

Explore →

Is Your Infrastructure Affected by CVE-2026-62368?

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

Book a Demo →Browse All CVEs