CVE-2026-86772 grokability CVE debrief

Who should care

Defenders responsible for Snipe-IT deployments should assess exposure and apply patches or workarounds to prevent exploitation. This includes IT administrators, security teams, and vulnerability management teams who oversee Snipe-IT installations. They should review the vulnerability details, verify the exposure of their systems, and take necessary actions to mitigate the risk. Additionally, they should monitor for suspicious activity and review compensing

Why it matters

CVE-2026-86772 is a stored cross-site scripting vulnerability in Snipe-IT versions before 8.7.0 that allows users with departments.edit permission to inject malicious scripts into department names, which can execute in the browsers of department members when they load their My Assets page.

• Potential for malicious scripts to be injected into department names and executed in the browsers of department members
• Possible impact on data confidentiality and integrity
• Need for defenders to verify exposure and apply patches or workarounds

Technical summary

The vulnerability exists in the DepartmentPresenter::formattedNameLink() method where department names are rendered unescaped in the fallback branch for users without departments.view permission. This allows users with departments.edit permission to inject malicious scripts into department names, which can execute in the browsers of department members when they load their My Assets page. The vulnerability affects Snipe-IT versions before 8.7.0 and has a CVSS score of 5.1, indicating a medium severity level. Defenders should prioritize verifying exposure and applying patches or workarounds to prevent exploitation.

Defensive priority

Defenders should prioritize verifying exposure and applying patches or workarounds to prevent exploitation.

Recommended defensive actions

• Verify Snipe-IT version and apply patch or workaround if necessary
• Restrict departments.edit permission to trusted users
• Monitor My Assets page for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is confirmed in Snipe-IT versions before 8.7.0. Users with departments.edit permission can inject malicious scripts into department names. Defenders should verify exposure and apply patches or workarounds. Evidence is limited to public sources and may not cover all affected systems or scenarios. Additional verification tasks are recommended.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.