{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-86764 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-86764 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-86764 is a high-severity missing authorization vulnerability in Snipeitapp Snipe-It, published on 9 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-86764 and fix it if it is affected.\n\nWhat it is: CVE-2026-86764 is a high-severity missing authorization vulnerability in Snipeitapp Snipe-It, published on 9 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-86764 in the wild and no public exploit code.\n\nAffected product: Snipeitapp Snipe-It. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-86764/ (Markdown: https://insights.sbomify.com/CVE-2026-86764/index.md)","id":"CVE-2026-86764","markdown":"https://insights.sbomify.com/CVE-2026-86764/index.md","name":"CVE-2026-86764","record":{"aliases":["GHSA-v46g-h6c9-wpq3","GHSA-v973-fm42-f8xv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IT asset management","requires_auth":"low_privilege","summary":"Authenticated users with asset view permissions can bypass component view restrictions to enumerate protected component details in Snipe-IT.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"snipe-it","vendor":"snipeitapp"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Snipe-IT through 8.6.4 (fixed in 8.7.0) does not enforce the components.view permission on the authenticated endpoint GET /api/v1/hardware/\u003casset-id\u003e/assigned/components. The endpoint authorizes only assets.view on the parent asset before returning linked component details; the components.view check is applied only to the response's available_actions.view flag and not to the returned data. As a result, an authenticated user holding only assets.view can enumerate component IDs, names, assigned quantities, and notes that are otherwise protected — the direct GET /api/v1/components/\u003cid\u003e endpoint correctly returns 403 Forbidden for such users.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Snipe-IT 8.6.4 before 8.7.0 Permission Bypass via assigned components","id":"CVE-2026-86764","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"snipeitapp:snipe-it","products":["snipeitapp:snipe-it"],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Snipe-IT 8.6.3 Authorization Bypass via Asset Update Endpoint","id":"CVE-2026-86765"},"packages":[],"prev":{"headline":"snipe-it 7.0.12 through 8.6.3 Authorization Bypass via Importer","id":"CVE-2026-86763"},"products":["snipe-it"],"published":"2026-09-09","related":[{"cvss_score":9.9,"headline":"File upload in n/a","id":"CVE-2025-63601","kev_date_added":null,"published":"2025-11-05"},{"cvss_score":9.8,"headline":"Snipe-IT has insecure permissions in file uploads","id":"CVE-2026-37709","kev_date_added":null,"published":"2026-05-07"},{"cvss_score":9.3,"headline":"Snipe-IT before 8.7.0 CSS Injection via Custom CSS","id":"CVE-2026-86738","kev_date_added":null,"published":"2026-09-08"},{"cvss_score":9.2,"headline":"Snipe-IT before 8.6.3 Authentication Bypass via Google SSO Callback","id":"CVE-2026-116199","kev_date_added":null,"published":"2026-10-25"},{"cvss_score":9.1,"headline":"Stored Cross Site Scripting vulnerability in Item name parameter in snipe/snipe-it","id":"CVE-2022-1380","kev_date_added":null,"published":"2022-04-16"},{"cvss_score":9,"headline":"Stored Cross Site Scripting vulnerability in the checked_out_to parameter in snipe/snipe-it","id":"CVE-2022-1445","kev_date_added":null,"published":"2022-04-24"},{"cvss_score":8.8,"headline":"Snipe-IT - Host Header Injection","id":"CVE-2022-23064","kev_date_added":null,"published":"2022-05-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-20","vendors":["grokability"]},"summary":"Authenticated users with asset view permissions can bypass component view restrictions to enumerate protected component details in Snipe-IT.","url":"https://insights.sbomify.com/CVE-2026-86764/"}