CVE-2026-55516

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Snipe-IT is an IT asset/license management system. Prior to 8.6.2, PATCH or PUT /api/v1/maintenances/{maintenance_id} checks access to the current maintenance record and asset but then fills attacker-controlled fields including asset_id without re-authorizing the newly supplied asset, allowing an authorized user to move a maintenance record onto an asset outside their company scope. This issue is fixed in version 8.6.2.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity77% × 45%
The EG Score, 7.7 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

July 10, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Jul 10, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Cross-company asset maintenance re-parenting via API update · Advisory · grokability/snipe-it · GitHub

https://github.com/grokability/snipe-it/security/advisories/GHSA-575r-357h-fhch
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 905d498ecdb0 (grokability/snipe-it)

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

https://github.com/grokability/snipe-it/commit/905d498ecdb0ee5591231c97bf48435e92044368

Vendor Advisories for CVE-2026-55516(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 rangeFix by version rangeDependents
snipe/snipe-it3.2.0 ... v8.6.1 (278 versions)
  • every version up to 8.6.2: fixed in 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 / 35× 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.

Showing the most recent 100 of 132 refreshes on record for this CVE.

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. None are among the latest 100 rows. The 32 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 19:39 UTCEG score recompute
  2. 2026-10-11 16:54 UTCEG score recompute
  3. 2026-10-11 14:17 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  7. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-10-01 15:07 UTCEG score recompute
  16. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-09-28 09:47 UTCEG score recompute
  20. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-09-24 11:10 UTCEG score recompute
  24. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-09-23 05:45 UTCEG score recompute
Show 75 more
  1. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-09-18 05:18 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-09-13 23:39 UTCEG score recompute
  9. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-09-12 15:19 UTCEG score recompute
  11. 2026-09-12 02:53 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-09-08 02:50 UTCEG score recompute
  16. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-09-06 13:57 UTCEG score recompute
  18. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-09-05 21:41 UTCEG score recompute
  20. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-08-30 06:23 UTCEG score recompute
  26. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  27. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  28. 2026-08-27 21:40 UTCEG score recompute
  29. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  30. 2026-08-27 00:47 UTCEG score recompute
  31. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  32. 2026-08-26 03:36 UTCEG score recompute
  33. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  34. 2026-08-24 20:14 UTCEG score recompute
  35. 2026-08-23 06:00 UTCEG score recompute
  36. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  37. 2026-08-22 05:08 UTCEG score recompute
  38. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  39. 2026-08-21 03:44 UTCEG score recompute
  40. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  41. 2026-08-20 01:32 UTCEG score recompute
  42. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  43. 2026-08-18 23:05 UTCEG score recompute
  44. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  45. 2026-08-17 22:11 UTCEG score recompute
  46. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  47. 2026-08-16 21:02 UTCEG score recompute
  48. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  49. 2026-08-16 08:36 UTCEG score recompute
  50. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  51. 2026-08-15 07:43 UTCEG score recompute
  52. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  53. 2026-08-14 05:26 UTCEG score recompute
  54. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  55. 2026-08-12 16:07 UTCEG score recompute
  56. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  57. 2026-08-11 15:11 UTCEG score recompute
  58. 2026-08-11 02:45 UTCEG score recompute
  59. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  60. 2026-08-10 01:54 UTCEG score recompute
  61. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  62. 2026-08-09 01:04 UTCEG score recompute
  63. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  64. 2026-08-08 00:12 UTCEG score recompute
  65. 2026-08-06 23:21 UTCEG score recompute
  66. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  67. 2026-08-05 22:29 UTCEG score recompute
  68. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  69. 2026-08-04 21:25 UTCEG score recompute
  70. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  71. 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  72. 2026-08-03 20:04 UTCEG score recompute
  73. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  74. 2026-08-02 06:35 UTCEG score recompute
  75. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.2% · 12th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55516?
CVE-2026-55516 is a high-severity vulnerability; its CVE record was published on July 10, 2026. Snipe-IT is an IT asset/license management system. Prior to 8.6.2, PATCH or PUT /api/v1/maintenances/{maintenanceid} checks access to the current maintenance record and asset but then fills attacker-controlled fields including assetid without re-authorizing the newly supplied asset, allowing an…
When was the CVE record for CVE-2026-55516 published?
The CVE record for CVE-2026-55516 was published on July 10, 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 July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-55516 actively exploited?
CVE-2026-55516 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-55516?
CVE-2026-55516 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55516?
A fix for CVE-2026-55516 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55516 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-55516

Explore →

Is Your Infrastructure Affected by CVE-2026-55516?

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

Book a Demo →Browse All CVEs