CVE-2025-36156
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 InfoSphere Data Replication VSAM for z/OS Remote Source 11.4 is vulnerable to a stack-based buffer overflow, caused by improper bounds checking. A local user with access to the files storing CECSUB or CECRM on the container could overflow the buffer and execute arbitrary code on 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 InfoSphere Data Replication VSAM for z/OS Remote Source 11.4 contains a stack-based buffer overflow vulnerability caused by improper bounds checking when processing CECSUB or CECRM files. A local user with access to these files on the container can overflow the buffer and execute arbitrary code on the system.
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= 11.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm installed versionLocate and inspect the installed version of IBM InfoSphere Data Replication VSAM for z/OS Remote Source. Use the product's version reporting mechanism or check the product's about/information panel.Affected if The installed version is 11.4 (the only affected version listed)
-
Identify CECSUB and CECRM filesSearch the filesystem for files named CECSUB or CECRM that are associated with the IBM InfoSphere Data Replication product. Check common product data directories and configuration locations.Affected if CECSUB or CECRM files exist in the environment and are accessible to local users
-
Verify file permissionsInspect the access permissions on any found CECSUB and CECRM files using standard file permission inspection tools appropriate to the operating system.Affected if CECSUB or CECRM files have broad permissions allowing access to untrusted local users
-
Check file processing configurationDetermine whether the product's feature that processes CECSUB or CECRM files is enabled or configured to run. Review product configuration settings related to CECSUB/CECRM file handling.Affected if The CECSUB/CECRM file processing feature is enabled and the product can be triggered to parse these files
You are affected if you have IBM InfoSphere Data Replication VSAM for z/OS Remote Source version 11.4 installed with CECSUB or CECRM files present and the file processing feature enabled, allowing local users to trigger the vulnerable code path.
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 dataApply IBM's vendor patch for this vulnerability. In the interim, restrict file-level access to CECSUB and CECRM files to minimize attack surface and follow least-privilege principles.
- Consultation8.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36156 — 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-36156 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