Finding and attribution
Snipe-IT’s importer checked a broad import permission but did not scope file and active-record queries by owner or company. An authenticated non-superuser with import permission could inspect other import records and load another user’s stored preview, including CSV headers and the first data row. In multi-company deployments, the preview could cross company boundaries. The maintainer advisory bounds disclosure to preview data, not the full CSV, and says superusers are unaffected. The CNA lists affected versions through 8.7.2, while the maintainer advisory says patched in 8.7.0; that discrepancy remains unresolved.
Product: snipe-it. AI system: AISLE AI-native discovery engine (specific model not identified). Team / organization: AISLE (self-attributed AI-engine discovery); VulnCheck CNA record.
CVE identifiers: CVE-2026-86763.
AI and human contribution (source account): The primary AISLE CVE-discoveries index explicitly scopes its listed cases as CVEs discovered by its AI-native engine and individually lists CVE-2026-86763. This is AISLE's self-attributed case-specific AI-engine claim. The available sources do not identify a model, establish autonomy or first-discovery priority, or define the human/tool work split.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The CNA record gives the public CVE publication date. The checked sources do not establish exploitation in the wild or zero-day status.
Remediation status: fix documented. The maintainer advisory states affected versions <=8.6.3 and patched 8.7.0. The CNA entry lists affected versions through 8.7.2, which conflicts with that advisory. The discrepancy is retained; no single global fixed boundary is asserted beyond the maintainer advisory’s stated patch.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 9 Sep 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Medium · highest recorded score 5.1. Documented technical effects: data disclosure.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-86763: CVSS 4.0 · 5.1 (Medium) ·
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N. CVE Program CNA record · checked 17 Nov 2026. - CVE-2026-86763: CVSS 3.1 · 3.5 (Low) ·
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N. CVE Program CNA record · checked 17 Nov 2026.
CVE-2026-86763: data disclosure.
Prerequisites / affected scope: snipe-it: 7.0.12 <= 8.7.2 affected.
Exploitation evidence: The CNA description establishes the stated technical effect. The checked CNA record does not report exploitation in the wild; no exploitability beyond the description is inferred.. Impact source · checked 17 Nov 2026.
Documented fix: The maintainer advisory states affected versions <=8.6.3 and patched 8.7.0. The CNA entry lists affected versions through 8.7.2, which conflicts with that advisory. The discrepancy is retained; no single global fixed boundary is asserted beyond the maintainer advisory’s stated patch.