dbcve.org
NahimicApplication · Steelseries

CVE-2025-68921

HIGH · 7.8 CVSS v3.1 Published 2026-01-16
Fix available
A fix is available. Upgrade to 1.10.4 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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
SteelSeries Nahimic 3 1.10.7 allows Directory traversal.

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 · moderate confidence

SteelSeries Nahimic 3 version 1.10.7 contains a directory traversal vulnerability that allows attackers to access files and directories outside the intended restricted path by manipulating file paths using '..' sequences or absolute paths.

MitigationImplement strict input validation and path canonicalization on all file path inputs to ensure paths resolve within allowed directories; validate and sanitize user-supplied path parameters before use in file operations.

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
NahimicApplication
Affected:< 1.10.4

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm SteelSeries Nahimic installation
    Check for Nahimic in installed programs: On Windows, open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell
    Affected if SteelSeries Nahimic appears in the installed programs list
  2. Identify installed Nahimic version
    Locate the Nahimic version from the registry key 'HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Nahimic' or check the executable properties of the Nahimic installation folder typically found in 'C:\Program Files\Nahimic\Nahimic3.exe'
    Affected if The displayed version number is less than 1.10.4 (e.g., 1.10.0, 1.10.1, 1.10.2, 1.10.3)
  3. Verify Nahimic service is active
    Open Services (services.msc) and locate 'Nahimic Service' or run 'Get-Service -Name Nahimic*' in PowerShell
    Affected if The Nahimic service status shows as Running while the version is below 1.10.4
  4. Identify vulnerable file handling component
    Examine the Nahimic installation directory for executable files that handle profile imports, audio settings, or configuration file operations - these are typically located in the main Nahimic installation folder
    Affected if File import or configuration load functionality exists in the Nahimic installation while running a version below 1.10.4

You are affected if SteelSeries Nahimic 3 is installed with a version lower than 1.10.4 and the Nahimic service is actively running, exposing the directory traversal vulnerability in file path handling.

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 1.10.4 or later
Fixed in 1.10.4
Interim mitigation

Implement strict input validation and path canonicalization on all file path inputs to ensure paths resolve within allowed directories; validate and sanitize user-supplied path parameters before use in file operations.

Recommended fix Moderate confidence

Nahimic version 1.10.4 or later

  1. 1. Open SteelSeries Nahimic application on your system
  2. 2. Navigate to the application settings or help section
  3. 3. Check the current installed version of Nahimic
  4. 4. If version is below 1.10.4, download the latest version from the official SteelSeries website (steelseries.com or steelseries.gg)
  5. 5. Run the installer and follow the on-screen prompts to update the software
  6. 6. Restart your computer after the update completes
  7. 7. Verify the installed version is 1.10.4 or higher
Caveat Standard update - no major breaking changes expected for typical users

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

Fix this in Nahimic Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68921 — 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-2025-68921 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