CVE Alert: CVE-2025-36156 – IBM – InfoSphere Data Replication VSAM for z/OS Remote Source

CVE-2025-36156

HIGHNo exploitation known

IBM 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.

CVSS v3.1 (7.4)
AV LOCAL · AC HIGH · PR NONE · UI NONE · S UNCHANGED
Vendor
IBM
Product
InfoSphere Data Replication VSAM for z/OS Remote Source
Versions
0 lte 11.4
CWE
CWE-119, CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Vector
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2025-10-07T17:36:57.964Z
Updated
2025-10-08T03:55:22.946Z
cpe:2.3:a:ibm:infosphere_data_replication:11.4:*:*:*:*:*:*:*

AI Summary Analysis

Risk verdict

High. Local code-execution is possible if an attacker can access the CECSUB/CECRM storage within the z/OS container; no known active exploitation, but the impact is severe.

Why this matters

If exploited, an attacker could achieve full system compromise affecting confidentiality, integrity and availability. In practice, this risks data leakage, tampering of replication workflows, or disruption of business-critical mainframe operations, especially in multi-tenant or shared-container environments.

Most likely attack path

Exploitation requires local access to the container storage; no privileges are required and no user interaction is needed. A successful stack overflow could allow arbitrary code execution within the targeted component, potentially enabling lateral movement within the host environment or containment bypass, given the high-impact CVSS metrics.

Who is most exposed

Mainframe environments with direct or loosely controlled local access to the CECSUB/CECRM files, particularly in multi-user or shared-container deployments, dev/test sandboxes, or where file permissions are lax.

Detection ideas

  • Frequent crashes or memory faults tied to the affected component.
  • Unexpected process behaviors or memory corruption traces in system logs.
  • Unusual code or execution patterns after accessing CECSUB/CECRM files.
  • Post-activity anomalies in replication workflows or job logs.
  • Confirmation of patch level against APAR PH67757.

Mitigation and prioritisation

  • Patch to the fixed release (APAR PH67757) or later; verify deployment in production testing.
  • If patching is constrained, tighten local access to CECSUB/CECRM storage and enforce least-privilege/file permissions.
  • Enable strict container isolation and monitor for anomalous memory/execution activity.
  • Validate integrity of CECSUB/CECRM files and security baselines before and after patching.
  • Change-management: schedule and test deployment; treat as priority 2 (no KEV/EPSS indication).

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.