CVE-2025-36133
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 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.
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 App Connect Enterprise Certified Container stores potentially sensitive information (such as credentials, API keys, or configuration secrets) in log files during the installation process. A local user with read access to the container can obtain this sensitive information from the logs, leading to information disclosure.
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= 12.0.9.0= 12.0.10.0= 12.0.11.1= 12.0.11.2= 12.0.11.3= 12.0.12= 12.0.12.0= 12.0.12.2= 12.0.12.3= 12.0.12.4= 12.0.12.5= 13.0.1.0>= 9.2.0, <= 11.6.0>= 12.0.0, < 12.15.0>= 12.1.0, < 12.15.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 App Connect Enterprise Certified Container versionCheck the image version or operand version deployed in your container environment. Run 'kubectl get pods' to find the operand pod, then inspect the container image tag or check the custom resource definition for the operand version.Affected if The installed version matches any of these: 12.0.9.0, 12.0.10.0, 12.0.11.1, 12.0.11.2, 12.0.11.3, 12.0.12, 12.0.12.0, 12.0.12.2, 12.0.12.3, 12.0.12.4, 12.0.12.5, or 13.0.1.0
-
Identify IBM App Connect Operator versionQuery the operator version in your cluster. Run 'kubectl get csv -n <namespace>' to find the operator CSV and check the version field, or inspect the operator deployment metadata.Affected if The operator version is >= 9.2.0 and <= 11.6.0, or >= 12.0.0 and < 12.15.0, or >= 12.1.0 and < 12.15.0
-
Locate installation log filesSearch for log files in the container filesystem. Common paths include /var/log, /tmp, or the working directory where installation scripts ran. Use 'find / -name "*.log" -mtime -<days>' to locate recently modified logs, or check persistent volume mounts used during installation.Affected if Log files exist from the container installation process and are readable by local users
-
Search for sensitive data in logsGrep through identified log files for patterns indicating credentials or secrets. Search for keywords like 'password', 'secret', 'key', 'token', 'credential', or look for base64-encoded strings and API keys. Use 'grep -iE '(password|secret|key|token|credential)' <logfile>' on each log file found.Affected if Log files contain plaintext or easily decoded credentials, API keys, or other secrets used during installation
Your environment is affected if you are running any of the listed versions AND installation logs containing sensitive information are readable by users with lower privileges than the container administrator.
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 · scoped12.15.0
Restrict log file permissions to prevent unauthorized local user access, and clean or rotate installation logs after setup. Update to a patched version if available from IBM.
Upgrade to IBM App Connect Enterprise Certified Containers version 12.15.0+ and App Connect Operator version 12.15.0+
- Identify the currently deployed IBM App Connect Enterprise Certified Container version using 'kubectl get pod' or container inspection
- Identify the currently deployed IBM App Connect Operator version using 'kubectl get subscriptions -n <namespace>'
- Upgrade IBM App Connect Enterprise Certified Containers to version 12.15.0 or later by updating the operand request or deployment configuration
- Upgrade IBM App Connect Operator to version 12.15.0 or later using Operator Lifecycle Manager (OLM) or via kubectl apply of the updated operator bundle
- Verify the upgrade was successful by checking the operator and operand versions post-upgrade
- Review container log configurations to ensure no sensitive information is being written to logs going forward
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36133 — 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-36133 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