dbcve.org
Snipe ItApplication · Snipeitapp

CVE-2026-55452

HIGH · 7.3 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 8.5.0 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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-privileged authenticated user to store a formula-like User-Agent that may execute when a report viewer opens the exported CSV in spreadsheet software. This issue is fixed in version 8.5.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Snipe-IT versions prior to 8.5.0 have a formula injection vulnerability where Actionlog::logaction() stores the raw User-Agent header without sanitization, and ReportsController::postActivityReport() exports this unsanitized value to CSV. A low-privileged authenticated user can inject spreadsheet formulas (e.g., =CMD|'') via the User-Agent header that execute when an admin opens the exported CSV in spreadsheet software.

MitigationUpgrade to Snipe-IT version 8.5.0 or later which implements proper formula escaping when writing User-Agent data to CSV exports.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Snipe ItApplication
Affected:< 8.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Snipe-IT version
    Locate the version file in the Snipe-IT installation directory or access the version information from the admin dashboard (typically at /api/v1/version or in the footer of the admin interface)
    Affected if the installed version is prior to 8.5.0
  2. Verify Actionlog feature is enabled
    Access Snipe-IT admin settings and check if action logging is enabled (usually found under System Settings or Logging settings)
    Affected if action logging is enabled and configured to capture User-Agent headers
  3. Confirm activity report export capability
    Navigate to the Reports section in Snipe-IT admin panel and verify if an Activity Report export option exists that includes User-Agent data
    Affected if the activity report export function is available and includes User-Agent fields in the output
  4. Inspect CSV export for unsanitized User-Agent
    As a low-privileged user, inject a test formula (e.g., =CMD|'') into your User-Agent header via browser dev tools or a curl request, then trigger the activity report export as an admin and open the resulting CSV in a spreadsheet application
    Affected if the CSV export contains the raw User-Agent string without formula escaping (cells starting with =, +, -, @, tab, or CR characters)

You are affected if Snipe-IT version is prior to 8.5.0, action logging captures User-Agent headers, and the activity report export displays raw User-Agent data without sanitization in the CSV output.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.5.0 or later
Fixed in 8.5.0
Interim mitigation

Upgrade to Snipe-IT version 8.5.0 or later which implements proper formula escaping when writing User-Agent data to CSV exports.

Recommended fix High confidence

8.5.0

  1. 1. Backup your current Snipe-IT installation and database before upgrading.
  2. 2. Download Snipe-IT version 8.5.0 from the official GitHub releases page (github.com/snipe/snipe-it).
  3. 3. Follow the standard Snipe-IT upgrade procedure: stop the web server, replace application files with the new version, run database migrations if required (php artisan migrate), then restart the web server.
  4. 4. Verify the upgrade was successful by logging in and checking the version number in the admin panel.
  5. 5. Test that the Activity Report export function properly escapes formulas in the User-Agent field by exporting a test report.
Caveat Review the Snipe-IT 8.5.0 release notes for any breaking changes or required configuration updates before upgrading.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Snipe It Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55452 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55452 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data