CVE-2025-36158
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 Concert 1.0.0 through 2.0.0 could allow a local user with specific permission to obtain sensitive information from files due to uncontrolled recursive directory copying.
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 Concert versions 1.0.0 through 2.0.0 contains a local information disclosure vulnerability where a user with specific permissions can exploit uncontrolled recursive directory copying to access sensitive files outside the intended scope, likely due to insufficient path traversal validation.
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, < 2.1.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify IBM Concert installationLocate IBM Concert installation directory and look for version information in product manifest, about dialog, or version file (commonly found in installation root or conf directory)Affected if IBM Concert is installed and version is 1.0.0 through 2.0.0 (less than 2.1.0)
-
Verify installed version numberRun command to retrieve version: 'concert --version' or check the version file in the installation directoryAffected if Version returned is >= 1.0.0 and < 2.1.0
-
Check user permissions for file operationsReview user role permissions in IBM Concert administration console or user configuration to determine if the account has permissions to perform file system or directory operationsAffected if User has permissions to access directory copy or file system operations functionality
-
Determine if directory copy feature is enabledInspect IBM Concert configuration files (such as concert.conf or settings.xml) to see if directory copy or recursive file operations module is enabled or accessibleAffected if Directory copy functionality is enabled and accessible to the user
Environment is affected if IBM Concert version is 1.0.0 through 2.0.0 (less than 2.1.0) AND the user has permissions to access the directory copy feature with path traversal capability.
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 · scoped2.1.0
Implement strict path validation and traversal prevention in the directory copy functionality to ensure copied paths remain within allowed boundaries; restrict and validate user permissions for file system operations.
2.1.0 or later
- Verify current IBM Concert version is below 2.1.0
- Contact IBM Support or consult official IBM Concert documentation to obtain the 2.1.0 or later release
- Upgrade IBM Concert to version 2.1.0 or later to remediate the vulnerability
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-36158 — 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-36158 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