CVE-2025-46616
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 · uneditedQuantum StorNext Web GUI API before 7.2.4 allows potential Arbitrary Remote Code Execution (RCE) via upload of a file. This affects StorNext RYO before 7.2.4, StorNext Xcellis Workflow Director before 7.2.4, and ActiveScale Cold Storage.
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 confidenceQuantum StorNext Web GUI API before 7.2.4 contains a file upload vulnerability that allows authenticated attackers to achieve arbitrary remote code execution on the affected system. The vulnerability affects StorNext RYO, StorNext Xcellis Workflow Director, and ActiveScale Cold Storage installations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed StorNext product and versionAccess the Web GUI or use command line tools (e.g., 'snmanufacture -v' or check /usr/local/quantum/config files) to determine the exact product name and software version running in your environmentAffected if The product is StorNext RYO, StorNext Xcellis Workflow Director, or ActiveScale Cold Storage and the version is earlier than 7.2.4
-
Verify the Web GUI API is accessibleCheck if the Web GUI interface is exposed by reviewing network configurations, firewall rules, or by attempting to access the API endpoint (typically port 3443 or 443 for HTTPS) from your internal networkAffected if The Web GUI API is reachable over the network (even internally) and authentication can be obtained
-
Confirm file upload functionality is enabledReview the Web GUI configuration settings or check for the presence of upload-related API endpoints (e.g., /api/upload or similar paths) in the service documentation or by inspecting available API methodsAffected if File upload functionality is available and enabled in the Web GUI configuration
You are affected if you run StorNext RYO, Xcellis Workflow Director, or ActiveScale Cold Storage with a version earlier than 7.2.4 where the Web GUI API is accessible and file upload features are enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to StorNext version 7.2.4 or later to remediate this vulnerability. For systems unable to upgrade immediately, restrict network access to the Web GUI API and disable file upload functionality if possible.
StorNext 7.2.4 (or later) for RYO, Xcellis Workflow Director, and ActiveScale Cold Storage
- Identify the currently installed Quantum StorNext version using the Web GUI or command line interface
- Plan for upgrade during a maintenance window as the Web GUI service may restart
- Download StorNext 7.2.4 or later from Quantum's support portal at www.quantum.com
- Follow Quantum's standard upgrade procedure for StorNext Web GUI API
- After upgrade, verify the new version is 7.2.4 or later in the Web GUI
- Validate that file upload functionality works correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46616 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-46616 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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