Is CVE-2026-55466 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55466 being exploited in the wild.

How severe is CVE-2026-55466?

High severity, with a CVSS score of 8.7, published 10 July 2026.

Which products and versions are affected?

snipe/snipe-it (Packagist) <= 8.6.1, ECOSYSTEM:introduced=0,fixed=8.6.2.

Is there a fix for CVE-2026-55466?

Yes. snipe/snipe-it (Packagist): upgrade to 8.6.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55466 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-55466?

Check whether you run snipe/snipe-it (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55466: Grokability Snipe-IT stored XSS in asset attachments

Q: Is there a fix for CVE-2026-55466?

Yes. snipe/snipe-it (Packagist): upgrade to 8.6.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-55466 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-55466?

Check whether you run snipe/snipe-it (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55466 · Severity: high · CVSS 8.7 · Published 2026-07-10

Snipe-IT is an asset management platform used to track and manage IT equipment and inventory. A flaw in its file upload and serving logic allows users with basic asset-viewing permissions to upload malicious XML files containing executable scripts. When these files are served back through the application, the browser executes the scripts with full access to user cookies and sessions, enabling attackers to steal admin credentials or impersonate other users. An attacker needs only low-level account access to exploit this vulnerability.

Technologies: snipe/snipe-it (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-55466 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55466 being exploited in the wild.
How severe is CVE-2026-55466?: High severity, with a CVSS score of 8.7, published 10 July 2026.
Which products and versions are affected?: snipe/snipe-it (Packagist) <= 8.6.1, ECOSYSTEM:introduced=0,fixed=8.6.2.
Is there a fix for CVE-2026-55466?: Yes. snipe/snipe-it (Packagist): upgrade to 8.6.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55466 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-55466?: Check whether you run snipe/snipe-it (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

snipe/snipe-it (Packagist): upgrade to 8.6.2 or later
```
composer require snipe/snipe-it:^8.6.2
```

Technical details

This is a stored cross-site scripting (XSS) vulnerability in Snipe-IT's file upload and serving mechanism. The root cause is a logic gap in upload validation: the UploadFileRequest sanitizer only triggers for files detected as image/svg+xml by PHP's finfo utility, but allows XML and other document types through without sanitization. An attacker creates an XHTML file (which PHP's finfo identifies as text/xml rather than image/svg+xml), bypassing the SVG sanitization step. The file is stored raw with any embedded <script> tags intact. When served inline via the UploadedFilesController with Content-Disposition: inline, the browser treats it as an executable XHTML document and runs the JavaScript in the same origin. The existing StorageHelper::allowSafeInline() whitelist exists but is never invoked in the serve path. An attacker requires only assets.view and assets.files permissions (low-privilege) and the target user must visit the malicious file URL with inline=true parameter. Patch version 8.6.2 fixes this by implementing proper content-type validation and sanitization.

Affected products

grokability snipe-it <= 8.6.1

Identifiers

CVE-2026-55466
GHSA-jhph-5q74-pmfx

Timeline

2026-06-24: disclosed
2026-08-28: advisory
2026: patched: Version 8.6.2 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.