CyberSecBulletin

Grokability vulnerabilities

We track 27 vulnerabilities in Grokability products. 27 are rated high or critical, and none are known to be exploited. The most recent was published on October 25, 2026.

27vulnerabilities
1critical
26high
0exploited
8.1average CVSS score

Latest Grokability vulnerabilities

  • 8.8 High severity

    snipe-it: Authentication Bypass by Capture-replay

    CVE-2026-116201Grokability

    Snipe-IT before 8.5.0 contains a SAML assertion replay vulnerability that allows attackers to reuse captured assertions by exploiting a non-atomic nonce check in the SAML acs handler. Attackers can send concurrent POST requests to /saml/acs with one captured a

  • 8.1 High severity

    snipe-it: Improper Authorization

    CVE-2026-116199Grokability

    Snipe-IT before 8.6.3 contains an authentication bypass in GoogleAuthController::handleGoogleCallback, which logs in the user whose username matches the Google account email without enforcing the activated flag. Deactivated users with email-shaped usernames an

  • 8.1 High severity

    snipe-it: Authentication Bypass Using an Alternate Path or Channel

    CVE-2026-63493Grokability

    Snipe-IT is an IT asset/license management system. Prior to 8.7.0, a password-authenticated session for an account with self.api permission can reach the personal-access-token API flow before completing the account's second-factor challenge because CheckForTwo

  • 8.4 High severity

    snipe-it: Improper Neutralization of Input During Web Page Generation

    CVE-2026-62368Grokability

    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

  • 7.6 High severity

    snipe-it: Server-Side Request Forgery

    CVE-2026-86771Grokability

    Snipe-IT versions before 8.7.0 fail to HTML-escape the employee_num field in the acceptance PDF generator, allowing attackers with users.edit permission to inject img tags into TCPDF's writeHTML() function. Attackers can craft a malicious employee_num value co

  • 8.1 High severity

    snipe-it: Improper Handling of Case Sensitivity

    CVE-2026-86770Grokability

    Snipe-IT before 8.7.0 fails to validate username case sensitivity during SAML authentication, allowing attackers to authenticate as different users by registering IdP accounts with accent or case variants of victim usernames. Attackers can exploit the default

  • 8.1 High severity

    snipe-it: Missing Authorization

    CVE-2026-86762Grokability

    Snipe-IT before 8.7.0 does not apply the CheckUserIsActivated middleware to the `api` middleware group in app/Http/Kernel.php, and deactivating a user does not revoke that user's Passport personal access tokens. As a result, although a deactivated account is c

  • 7.1 High severity

    snipe-it: Missing Authorization

    CVE-2026-86759Grokability

    Snipe-IT versions before 8.7.0 fail to authorize the POST /hardware/history endpoint, allowing any authenticated user to reassign arbitrary assets and modify audit logs. Attackers can submit a CSV file to reassign assets across companies and inject fraudulent

  • 7.3 High severity

    snipe-it: Incorrect Authorization

    CVE-2026-86754Grokability

    Snipe-IT before 8.7.0 fails to properly gate Laravel Passport's OAuth client management routes, allowing any authenticated user to register OAuth clients with attacker-controlled redirect URIs. Attackers can trick administrators into approving consent screens,

  • 9.6 Critical severity

    snipe-it: External Control of File Name or Path

    CVE-2026-86751Grokability

    Snipe-IT before 8.7.0 fails to properly sanitize markdown image syntax in note fields, allowing authenticated users to read arbitrary server files and issue server-side HTTP requests. Attackers can submit markdown image syntax in checkout acceptance notes that

  • 7.7 High severity

    snipe-it: Incorrect Authorization

    CVE-2026-86750Grokability

    Snipe-IT versions <= 8.6.3 (fixed in 8.7.0) do not validate company assignment authorization before persisting user records via the REST API. In Api\UsersController::store() and ::update(), the user record is filled from the request and saved before the reques

  • 8.5 High severity

    snipe-it: External Control of File Name or Path

    CVE-2026-86741Grokability

    Snipe-IT versions before 8.7.0 fail to sanitize the category EULA text field before rendering it in checkout confirmation emails. Attackers with low-privilege permissions can inject markdown image syntax or raw HTML img tags pointing to local files or remote U

  • 8.7 High severity

    snipe-it: Improper Neutralization of Input During Web Page Generation

    CVE-2026-86738Grokability

    Snipe-IT versions before 8.7.0 contain a CSS injection vulnerability in the Custom CSS field due to incomplete sanitization that reverses HTML encoding on greater-than and double-quote characters. Superusers can plant malicious CSS payloads using @import and u

  • 7.2 High severity

    snipe-it: Improper Neutralization of Special Elements used in an OS Command

    CVE-2026-86733Grokability

    Snipe-IT before 8.7.0 streams the SQL entry from an uploaded backup archive directly into the MySQL/MariaDB command-line client (`mysql`) without the --binary-mode flag, so the client interprets lines beginning with backslash commands such as `\!` as local she

  • 8.8 High severity

    snipe-it: Authorization Bypass Through User-Controlled Key

    CVE-2026-85617Grokability

    snipe-it versions before 8.6.3 contain an authorization bypass vulnerability in the bulk delete functionality that allows restricted users to soft-delete users outside their authorized scope. Attackers can include unauthorized user IDs in bulk delete requests

  • 8.5 High severity

    snipe-it: Authorization Bypass Through User-Controlled Key

    CVE-2026-85616Grokability

    Snipe-IT versions before 8.6.2 contain an authorization bypass vulnerability in checkout-acceptance report actions when Full Multiple Company Support is enabled. Authenticated users with reports.view permission can enumerate sequential acceptance IDs and soft-

  • 8.8 High severity

    snipe-it: Incorrect Authorization

    CVE-2026-55643Grokability

    Snipe-IT is an IT asset/license management system. Prior to 8.6.3, a company-scoped user in FMCS floater mode can access users whose company_id is null because broad API queries and bulk web actions do not consistently apply isCurrentUserHasAccess. The /api/v1

  • 8.8 High severity

    snipe-it: Missing Authorization

    CVE-2026-55483Grokability

    Snipe-IT is an IT asset/license management system. Prior to 8.6.0, an authenticated user with users.create permission can submit the admin permission while creating a user because store() in app/Http/Controllers/Users/UsersController.php strips superuser permi

  • 8.7 High severity

    snipe-it: Improper Neutralization of Input During Web Page Generation

    CVE-2026-55466Grokability

    Snipe-IT is an IT asset/license management system. Prior to 8.6.2, UploadFileRequest sanitizes SVG content only when PHP finfo reports image/svg+xml and UploadedFilesController serves attachments inline without using StorageHelper::allowSafeInline(), allowing

  • 7.3 High severity

    snipe-it: Improper Neutralization of Formula Elements in a CSV File

    CVE-2026-55452Grokability

    Snipe-IT is an IT asset/license management system. Prior to 8.5.0, Actionlog::logaction() stores the request User-Agent header and ReportsController::postActivityReport() writes that value to the Activity Report CSV without formula escaping, allowing a low-pri

  • 7.7 High severity

    snipe-it: Authorization Bypass Through User-Controlled Key

    CVE-2026-55516Grokability

    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

  • 7.1 High severity

    snipe-it: Incorrect Authorization

    CVE-2026-55460Grokability

    Snipe-IT is an IT asset/license management system. Prior to 8.6.2, an authenticated non-admin user with users.view and users.edit but without users.delete can directly POST to /users/bulksave with delete_user=1 because BulkUsersController::destroy() authorizes

  • 7.7 High severity

    snipe-it: Missing Authorization

    CVE-2026-54329Grokability

    Snipe-IT is an IT asset/license management system. Prior to 8.6.2, the Accessories API create path mass-assigns request parameters to the Accessory model while company_id is mass assignable, allowing a low-privileged authenticated user in one company to create

  • 7.1 High severity

    snipe-it: Incorrect Authorization

    CVE-2026-48507Grokability

    Snipe-IT is an IT asset/license management system. A vulnerability in versions prior to 8.6.0 allows a non-admin user holding only the granular `users.edit` permission to lock every admin out of the instance by editing the `activated` flag (which determines wh

  • 7.1 High severity

    snipe-it: URL Redirection to Untrusted Site

    CVE-2026-44833Grokability

    Snipe-IT is an IT asset/license management system. Prior to 8.4.1, an open redirect vulnerability in Snipe-IT allows attackers to redirect users to malicious sites via unvalidated HTTP Referer header stored in session variable. This vulnerability is fixed in 8

  • 8.8 High severity

    snipe-it: Improper Preservation of Permissions

    CVE-2026-44832Grokability

    Snipe-IT is an IT asset/license management system. Prior to 8.4.1, aAn authenticated user with only users.edit permission can escalate their own privileges to admin by sending a PATCH request to /api/v1/users/{id} with permissions[admin]=1. The API controller

  • 8.8 High severity

    Snipe-IT: Improperly Controlled Modification of Dynamically-Determined Object Attributes

    CVE-2025-15602Grokability

    Snipe-IT versions prior to 8.3.7 contain sensitive user attributes related to account privileges that are insufficiently protected against mass assignment. An authenticated, low-privileged user can craft a malicious API request to modify restricted fields of a