CVE-2025-36074
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 Security Verify Directory (Container) 10.0.0 through 10.0.0.3 IBM Security Verify Directory could be vulnerable to malicious file upload by not validating file type. A privileged user could upload malicious files into the system that can be sent to victims for performing further attacks against the system.
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 confidenceIBM Security Verify Directory (Container) versions 10.0.0 through 10.0.0.3 lacks proper file type validation on file uploads, allowing authenticated privileged users to upload arbitrary file types. These malicious files can be served to victims, enabling further attacks such as stored XSS 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>= 10.0.0, <= 10.0.3CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of IBM Security Verify DirectoryCheck the container image tag or running container version using 'docker images' or 'kubectl get pods' with version details, or access the product's about/admin panel to view the version numberAffected if version is 10.0.0, 10.0.0.1, 10.0.0.2, or 10.0.0.3 (any version between 10.0.0 and 10.0.0.3 inclusive)
-
Confirm file upload functionality is accessibleLocate any file upload endpoints in the web interface or API documentation for IBM Security Verify Directory, typically found in user profile settings, document management, or attachment featuresAffected if file upload feature is enabled and accessible to authenticated users in the environment
-
Check for server-side file type validationReview the application's file upload configuration or proxy settings for any validation mechanisms such as magic byte checks, MIME type validation, or extension allowlistsAffected if no server-side file type validation is configured, or validation can be bypassed by uploading non-image/non-document files
-
Verify uploaded files are stored outside webrootInspect the file storage configuration or container volume mounts to determine where uploaded files are persisted relative to the web server rootAffected if uploaded files are stored within the webroot and accessible via HTTP/HTTPS URLs
Your environment is affected if you are running IBM Security Verify Directory (Container) versions 10.0.0 through 10.0.0.3 with the file upload feature enabled and without proper server-side file type validation in place.
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.
From vendor dataImplement server-side validation of file types using magic byte checks, MIME type validation, and strict allowlist of permitted extensions. Store uploaded files outside webroot with proper Content-Disposition headers to prevent execution.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36074 — 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-36074 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