Skip to main content
VulnerabilityPublished Updated

CVE-2025-36133: IBM App Connect Enterprise Certified Container · Sensitive Data in Logs

Affects IBM App Connect Enterprise Certified ContainerSource CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBM App Connect Enterprise Certified ContainerAffected
  • =9.2.0
  • =12.0.0
  • =12.1.0
Fixed in–

AI-suggested

To mitigate CVE-2025-36133, European organizations should implement the following specific measures: 1) Restrict and tightly control access to container environments running IBM App Connect Enterprise, ensuring only authorized personnel have local access. 2) Monitor and audit container access logs to detect any unauthorized or suspicious local access attempts. 3) Employ container security best practices such as running containers with least privilege, using read-only file systems where possible, and isolating containers to minimize lateral movement. 4) Review and sanitize log files generated during installation to remove or mask sensitive information, or configure logging to exclude sensitive data if supported. 5) Stay alert for IBM security advisories and apply patches or updates promptly once available. 6) Use secrets management solutions external to the container to avoid embedding sensitive information in installation processes or logs. 7) Conduct regular security assessments of container configurations and deployment pipelines to identify and remediate potential information leakage vectors.

Description

IBM App Connect Enterprise Certified Container CD: 9.2.0 through 11.6.0, 12.1.0 through 12.14.0, and 12.0 LTS: 12.0.0 through 12.0.14stores potentially sensitive information in log files during installation that could be read by a local user on the container.

References

Community reviews

Loading reviews…