CVE-2025-36174
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 · uneditedIBM Integrated Analytics System 1.0.0.0 through 1.0.30.0 could allow an authenticated user to upload a file with dangerous types that could be executed by another user if opened.
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 confidenceIBM Integrated Analytics System versions 1.0.0.0 through 1.0.30.0 contains a file upload vulnerability where authenticated users can upload files with dangerous types (e.g., executables, scripts) that may be executed by other users who open them, leading to potential code execution or malware delivery.
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>= 1.0.0.0, <= 1.0.31.0CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Determine IBM Integrated Analytics System versionAccess the system administration console or use the system's version command-line tool to retrieve the installed version number. Check the 'About' or 'System Information' section in the IBM Integrated Analytics System management interface.Affected if The installed version falls within >= 1.0.0.0 and <= 1.0.31.0
-
Confirm authenticated user access to file upload featureLog into IBM Integrated Analytics System with a standard authenticated user account (non-admin). Navigate to the file upload or data import functionality within the system interface. Verify whether a standard authenticated user can access and use the file upload capability.Affected if Authenticated users have access to a file upload interface or API endpoint in the system
-
Inspect file upload validation controlsExamine the system's file upload configuration or documentation for file type restrictions. If possible, attempt to upload a test file with a potentially dangerous extension (such as .exe, .js, .bat, .sh, .php) using an authenticated user session. Observe whether the system accepts or rejects the upload based on file extension or MIME type.Affected if The system allows upload of executable or script file types (.exe, .js, .bat, .sh, .php, etc.) without validation or blocks only a very narrow set of types leaving dangerous ones permitted
A user is affected if they run IBM Integrated Analytics System version 1.0.0.0 through 1.0.31.0 and the file upload feature is accessible to authenticated users without proper file type validation.
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 · scopedImplement strict file type validation on upload, restrict dangerous file extensions/types, and sanitize stored filenames; consider adding warning dialogs or disabling automatic execution for uploaded files.
IBM Integrated Analytics System 1.0.31.0 or later
- 1. Identify the current IBM Integrated Analytics System version in your environment.
- 2. Plan for upgrade during a maintenance window with appropriate backup procedures.
- 3. Download IBM Integrated Analytics System version 1.0.31.0 or later from IBM Fix Central or your entitled IBM software repository.
- 4. Follow IBM's standard upgrade documentation for Integrated Analytics System, ensuring all prerequisites are met.
- 5. After upgrade, verify that file upload functionality works correctly and that dangerous file types are properly restricted.
- 6. Confirm the new version by checking the system information or using IBM's version verification tools.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36174 — 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-36174 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