{"items":[{"id":"NVI-00007171","kind":"vulnerability","title":"Snipe-IT vulnerable to cross-company asset maintenance re-parenting via API update","revision":5,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-575r-357h-fhch","CVE-2026-55516"],"plain_summary":"GitHub lists this reviewed advisory for snipe/snipe-it. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-009e83bd30907540ca6cd27c1bd56869"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 8.6.2 for snipe/snipe-it. Confirm the publisher’s latest guidance.","source_ids":["sr-d1c588c17045c34a8f611e64afc78106"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-28T18:06:06.000Z","value":"7.7 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0987407d52dfaf35defd372379140dde"},{"kind":"CVSS","as_of":"2026-10-25T15:10:00.147Z","value":"7.7 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-710e97ec458b2d5672d7b4636b81c0f7"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.376%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.31631. Missing scores are unknown.","source_id":"sr-009e83bd30907540ca6cd27c1bd56869"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0987407d52dfaf35defd372379140dde","url":"https://github.com/advisories/GHSA-575r-357h-fhch","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-575r-357h-fhch","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T09:56:23.004Z"},{"id":"sr-d1c588c17045c34a8f611e64afc78106","url":"https://github.com/advisories/GHSA-575r-357h-fhch","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-575r-357h-fhch","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.678Z"},{"id":"sr-710e97ec458b2d5672d7b4636b81c0f7","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55516","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-55516","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:39.943Z"},{"id":"sr-009e83bd30907540ca6cd27c1bd56869","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-55516","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.788Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0987407d52dfaf35defd372379140dde"],"technology":"snipe/snipe-it","known_exclusions":[],"conditions_summary":"### Impact\nThe API endpoint for updating asset maintenance records allows an authorized user to change the asset_id of an existing maintenance record to an asset outside their company scope.\n\nIn a Full Multiple Company Support / multi-company deployment, this allows a user from Company A to attach or move a maintenance record onto an asset belonging to Company B. The endpoint appears to authorize access to the existing maintenance record’s asset, but does not re-authorize the newly supplied asset_id before saving the update.\n\n###  Affected endpoint\n`PATCH /api/v1/maintenances/{maintenance_id}`\n\nAlso likely affected:\n\n`PUT /api/v1/maintenances/{maintenance_id}`\n\n### Preconditions\nThe attacker needs:\n- A valid authenticated API token.\n- Permission to update asset maintenance records.\n- Access to a maintenance record currently attached to an asset in their own company.\n\nThe attacker does not need access to the target asset’s company.\n\n### Root cause\nIn the API maintenance update flow, the application checks access to the current maintenance record / current asset, then accepts attacker-controlled fields including `asset_id`.\n\nThe vulnerable behavior is that the new asset_id is not che","public_affected_ranges":["<= 8.6.1"]},{"certainty":"source_listed","source_ids":["sr-d1c588c17045c34a8f611e64afc78106"],"technology":"snipe/snipe-it","known_exclusions":[],"conditions_summary":"### Impact\nThe API endpoint for updating asset maintenance records allows an authorized user to change the asset_id of an existing maintenance record to an asset outside their company scope.\n\nIn a Full Multiple Company Support / multi-company deployment, this allows a user from Company A to attach or move a maintenance record onto an asset belonging to Company B. The endpoint appears to authorize access to the existing maintenance record’s asset, but does not re-authorize the newly supplied asset_id before saving the update.\n\n###  Affected endpoint\n`PATCH /api/v1/maintenances/{maintenance_id}`\n\nAlso likely affected:\n\n`PUT /api/v1/maintenances/{maintenance_id}`\n\n### Preconditions\nThe attacker needs:\n- A valid authenticated API token.\n- Permission to update asset maintenance records.\n- Access to a maintenance record currently attached to an asset in their own company.\n\nThe attacker does not need access to the target asset’s company.\n\n### Root cause\nIn the API maintenance update flow, the application checks access to the current maintenance record / current asset, then accepts attacker-controlled fields including `asset_id`.\n\nThe vulnerable behavior is that the new asset_id is not che","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 8.6.2"]}],"null_published_at":"2026-11-04T10:04:35.955Z","source_updated_at":"2026-08-28T18:06:06.000Z","source_disclosed_at":"2026-08-28T18:06:05.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:49.678Z"},{"id":"NVI-00007171","kind":"vulnerability","title":"Snipe-IT vulnerable to cross-company asset maintenance re-parenting via API update","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-575r-357h-fhch","CVE-2026-55516"],"plain_summary":"GitHub lists this reviewed advisory for snipe/snipe-it. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-5e09413433fca03ffa8f5503e375572b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 8.6.2 for snipe/snipe-it. Confirm the publisher’s latest guidance.","source_ids":["sr-d1c588c17045c34a8f611e64afc78106"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-28T18:06:06.000Z","value":"7.7 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0987407d52dfaf35defd372379140dde"},{"kind":"CVSS","as_of":"2026-10-25T15:10:00.147Z","value":"7.7 HIGH (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-710e97ec458b2d5672d7b4636b81c0f7"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.376%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.31593. Missing scores are unknown.","source_id":"sr-5e09413433fca03ffa8f5503e375572b"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0987407d52dfaf35defd372379140dde","url":"https://github.com/advisories/GHSA-575r-357h-fhch","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-575r-357h-fhch","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T09:56:23.004Z"},{"id":"sr-d1c588c17045c34a8f611e64afc78106","url":"https://github.com/advisories/GHSA-575r-357h-fhch","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-575r-357h-fhch","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.678Z"},{"id":"sr-710e97ec458b2d5672d7b4636b81c0f7","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55516","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-55516","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:39.943Z"},{"id":"sr-5e09413433fca03ffa8f5503e375572b","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-55516","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.383Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0987407d52dfaf35defd372379140dde"],"technology":"snipe/snipe-it","known_exclusions":[],"conditions_summary":"### Impact\nThe API endpoint for updating asset maintenance records allows an authorized user to change the asset_id of an existing maintenance record to an asset outside their company scope.\n\nIn a Full Multiple Company Support / multi-company deployment, this allows a user from Company A to attach or move a maintenance record onto an asset belonging to Company B. The endpoint appears to authorize access to the existing maintenance record’s asset, but does not re-authorize the newly supplied asset_id before saving the update.\n\n###  Affected endpoint\n`PATCH /api/v1/maintenances/{maintenance_id}`\n\nAlso likely affected:\n\n`PUT /api/v1/maintenances/{maintenance_id}`\n\n### Preconditions\nThe attacker needs:\n- A valid authenticated API token.\n- Permission to update asset maintenance records.\n- Access to a maintenance record currently attached to an asset in their own company.\n\nThe attacker does not need access to the target asset’s company.\n\n### Root cause\nIn the API maintenance update flow, the application checks access to the current maintenance record / current asset, then accepts attacker-controlled fields including `asset_id`.\n\nThe vulnerable behavior is that the new asset_id is not che","public_affected_ranges":["<= 8.6.1"]},{"certainty":"source_listed","source_ids":["sr-d1c588c17045c34a8f611e64afc78106"],"technology":"snipe/snipe-it","known_exclusions":[],"conditions_summary":"### Impact\nThe API endpoint for updating asset maintenance records allows an authorized user to change the asset_id of an existing maintenance record to an asset outside their company scope.\n\nIn a Full Multiple Company Support / multi-company deployment, this allows a user from Company A to attach or move a maintenance record onto an asset belonging to Company B. The endpoint appears to authorize access to the existing maintenance record’s asset, but does not re-authorize the newly supplied asset_id before saving the update.\n\n###  Affected endpoint\n`PATCH /api/v1/maintenances/{maintenance_id}`\n\nAlso likely affected:\n\n`PUT /api/v1/maintenances/{maintenance_id}`\n\n### Preconditions\nThe attacker needs:\n- A valid authenticated API token.\n- Permission to update asset maintenance records.\n- Access to a maintenance record currently attached to an asset in their own company.\n\nThe attacker does not need access to the target asset’s company.\n\n### Root cause\nIn the API maintenance update flow, the application checks access to the current maintenance record / current asset, then accepts attacker-controlled fields including `asset_id`.\n\nThe vulnerable behavior is that the new asset_id is not che","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 8.6.2"]}],"null_published_at":"2026-11-02T20:21:10.326Z","source_updated_at":"2026-08-28T18:06:06.000Z","source_disclosed_at":"2026-08-28T18:06:05.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:49.678Z"},{"id":"NVI-00007171","kind":"vulnerability","title":"Snipe-IT vulnerable to cross-company asset maintenance re-parenting via API update","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-575r-357h-fhch","CVE-2026-55516"],"plain_summary":"GitHub lists this reviewed advisory for snipe/snipe-it. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-5e09413433fca03ffa8f5503e375572b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 8.6.2 for snipe/snipe-it. Confirm the publisher’s latest guidance.","source_ids":["sr-d1c588c17045c34a8f611e64afc78106"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-28T18:06:06.000Z","value":"7.7 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-0987407d52dfaf35defd372379140dde"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.376%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.31593. Missing scores are unknown.","source_id":"sr-5e09413433fca03ffa8f5503e375572b"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-0987407d52dfaf35defd372379140dde","url":"https://github.com/advisories/GHSA-575r-357h-fhch","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-575r-357h-fhch","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T09:56:23.004Z"},{"id":"sr-d1c588c17045c34a8f611e64afc78106","url":"https://github.com/advisories/GHSA-575r-357h-fhch","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-575r-357h-fhch","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.678Z"},{"id":"sr-5e09413433fca03ffa8f5503e375572b","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-55516","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.383Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0987407d52dfaf35defd372379140dde"],"technology":"snipe/snipe-it","known_exclusions":[],"conditions_summary":"### Impact\nThe API endpoint for updating asset maintenance records allows an authorized user to change the asset_id of an existing maintenance record to an asset outside their company scope.\n\nIn a Full Multiple Company Support / multi-company deployment, this allows a user from Company A to attach or move a maintenance record onto an asset belonging to Company B. The endpoint appears to authorize access to the existing maintenance record’s asset, but does not re-authorize the newly supplied asset_id before saving the update.\n\n###  Affected endpoint\n`PATCH /api/v1/maintenances/{maintenance_id}`\n\nAlso likely affected:\n\n`PUT /api/v1/maintenances/{maintenance_id}`\n\n### Preconditions\nThe attacker needs:\n- A valid authenticated API token.\n- Permission to update asset maintenance records.\n- Access to a maintenance record currently attached to an asset in their own company.\n\nThe attacker does not need access to the target asset’s company.\n\n### Root cause\nIn the API maintenance update flow, the application checks access to the current maintenance record / current asset, then accepts attacker-controlled fields including `asset_id`.\n\nThe vulnerable behavior is that the new asset_id is not che","public_affected_ranges":["<= 8.6.1"]},{"certainty":"source_listed","source_ids":["sr-d1c588c17045c34a8f611e64afc78106"],"technology":"snipe/snipe-it","known_exclusions":[],"conditions_summary":"### Impact\nThe API endpoint for updating asset maintenance records allows an authorized user to change the asset_id of an existing maintenance record to an asset outside their company scope.\n\nIn a Full Multiple Company Support / multi-company deployment, this allows a user from Company A to attach or move a maintenance record onto an asset belonging to Company B. The endpoint appears to authorize access to the existing maintenance record’s asset, but does not re-authorize the newly supplied asset_id before saving the update.\n\n###  Affected endpoint\n`PATCH /api/v1/maintenances/{maintenance_id}`\n\nAlso likely affected:\n\n`PUT /api/v1/maintenances/{maintenance_id}`\n\n### Preconditions\nThe attacker needs:\n- A valid authenticated API token.\n- Permission to update asset maintenance records.\n- Access to a maintenance record currently attached to an asset in their own company.\n\nThe attacker does not need access to the target asset’s company.\n\n### Root cause\nIn the API maintenance update flow, the application checks access to the current maintenance record / current asset, then accepts attacker-controlled fields including `asset_id`.\n\nThe vulnerable behavior is that the new asset_id is not che","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 8.6.2"]}],"null_published_at":"2026-11-02T10:00:37.154Z","source_updated_at":"2026-08-28T18:06:06.000Z","source_disclosed_at":"2026-08-28T18:06:05.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:49.678Z"},{"id":"NVI-00007171","kind":"vulnerability","title":"Snipe-IT vulnerable to cross-company asset maintenance re-parenting via API update","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-575r-357h-fhch","CVE-2026-55516"],"plain_summary":"OSV carries this publisher advisory for snipe/snipe-it. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 8.6.2 for snipe/snipe-it. Confirm the publisher’s latest guidance.","source_ids":["sr-d1c588c17045c34a8f611e64afc78106"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-5e09413433fca03ffa8f5503e375572b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.376%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.31593. Missing scores are unknown.","source_id":"sr-5e09413433fca03ffa8f5503e375572b"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-d1c588c17045c34a8f611e64afc78106","url":"https://github.com/advisories/GHSA-575r-357h-fhch","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-575r-357h-fhch","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.678Z"},{"id":"sr-5e09413433fca03ffa8f5503e375572b","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-55516","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.383Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-d1c588c17045c34a8f611e64afc78106"],"technology":"snipe/snipe-it","known_exclusions":[],"conditions_summary":"### Impact\nThe API endpoint for updating asset maintenance records allows an authorized user to change the asset_id of an existing maintenance record to an asset outside their company scope.\n\nIn a Full Multiple Company Support / multi-company deployment, this allows a user from Company A to attach or move a maintenance record onto an asset belonging to Company B. The endpoint appears to authorize access to the existing maintenance record’s asset, but does not re-authorize the newly supplied asset_id before saving the update.\n\n###  Affected endpoint\n`PATCH /api/v1/maintenances/{maintenance_id}`\n\nAlso likely affected:\n\n`PUT /api/v1/maintenances/{maintenance_id}`\n\n### Preconditions\nThe attacker needs:\n- A valid authenticated API token.\n- Permission to update asset maintenance records.\n- Access to a maintenance record currently attached to an asset in their own company.\n\nThe attacker does not need access to the target asset’s company.\n\n### Root cause\nIn the API maintenance update flow, the application checks access to the current maintenance record / current asset, then accepts attacker-controlled fields including `asset_id`.\n\nThe vulnerable behavior is that the new asset_id is not che","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 8.6.2"]}],"null_published_at":"2026-11-01T01:45:38.528Z","source_updated_at":"2026-08-28T18:15:06.223Z","source_disclosed_at":"2026-08-28T18:06:05.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:49.678Z"},{"id":"NVI-00007171","kind":"vulnerability","title":"Snipe-IT vulnerable to cross-company asset maintenance re-parenting via API update","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-575r-357h-fhch","CVE-2026-55516"],"plain_summary":"OSV carries this publisher advisory for snipe/snipe-it. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 8.6.2 for snipe/snipe-it. Confirm the publisher’s latest guidance.","source_ids":["sr-d1c588c17045c34a8f611e64afc78106"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-d1c588c17045c34a8f611e64afc78106","url":"https://github.com/advisories/GHSA-575r-357h-fhch","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-575r-357h-fhch","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.678Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-d1c588c17045c34a8f611e64afc78106"],"technology":"snipe/snipe-it","known_exclusions":[],"conditions_summary":"### Impact\nThe API endpoint for updating asset maintenance records allows an authorized user to change the asset_id of an existing maintenance record to an asset outside their company scope.\n\nIn a Full Multiple Company Support / multi-company deployment, this allows a user from Company A to attach or move a maintenance record onto an asset belonging to Company B. The endpoint appears to authorize access to the existing maintenance record’s asset, but does not re-authorize the newly supplied asset_id before saving the update.\n\n###  Affected endpoint\n`PATCH /api/v1/maintenances/{maintenance_id}`\n\nAlso likely affected:\n\n`PUT /api/v1/maintenances/{maintenance_id}`\n\n### Preconditions\nThe attacker needs:\n- A valid authenticated API token.\n- Permission to update asset maintenance records.\n- Access to a maintenance record currently attached to an asset in their own company.\n\nThe attacker does not need access to the target asset’s company.\n\n### Root cause\nIn the API maintenance update flow, the application checks access to the current maintenance record / current asset, then accepts attacker-controlled fields including `asset_id`.\n\nThe vulnerable behavior is that the new asset_id is not che","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 8.6.2"]}],"null_published_at":"2026-10-31T22:13:14.315Z","source_updated_at":"2026-08-28T18:15:06.223Z","source_disclosed_at":"2026-08-28T18:06:05.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:49.678Z"}],"next_cursor":null,"snapshot_revision":"42594"}