CVE-2026-3602
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 13.0.1.0 through 13.0.7.2, and 12.0.1.0 through 12.0.12.26 and IBM Integration Bus for z/OS 10.1.0.0 through 10.1.0.7 is vulnerable to SQL injection. A remote attacker could socially engineer a user into accidentally creating files they may not be aware of.
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 confidenceSQL injection vulnerability in IBM App Connect Enterprise (versions 13.0.1.0-13.0.7.2 and 12.0.1.0-12.0.12.26) and IBM Integration Bus for z/OS (versions 10.1.0.0-10.1.0.7) allows remote attackers to inject malicious SQL code through socially engineered user actions, potentially causing unauthorized file creation 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>= 12.0.1.0, < 12.0.12.27>= 13.0.1.0, < 13.0.8.0>= 10.1.0.0, <= 10.1.0.7CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 the installed IBM product and versionRun the appropriate version reporting command for the product (such as mqsireportversion for IBM Integration Bus or the equivalent for App Connect Enterprise) to determine the exact version numberAffected if The installed version falls within 12.0.1.0-12.0.12.26, 13.0.1.0-13.0.7.2, or 10.1.0.0-10.1.0.7
-
Confirm product typeVerify whether the system is running IBM App Connect Enterprise or IBM Integration Bus for z/OS, as both product lines are affectedAffected if The product is either IBM App Connect Enterprise or IBM Integration Bus for z/OS within the stated version ranges
-
Check for database integrationsReview integration flows and configurations for any database connections or SQL query operations that process user-supplied inputAffected if Database integrations exist and accept input that could be manipulated through social engineering tricking users into file creation actions
-
Audit recent user activity logsReview audit logs for any suspicious file creation operations that users may have been tricked into performing unexpectedlyAffected if Users have been tricked into creating files they were not aware of, which could indicate exploitation attempts
You are affected if your installed version of IBM App Connect Enterprise is 12.0.1.0 through 12.0.12.26 or 13.0.1.0 through 13.0.7.2, or if IBM Integration Bus for z/OS is 10.1.0.0 through 10.1.0.7, and the system has database integrations that could be exploited through social engineering.
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.0.12.2713.0.8.0
Apply IBM security patches for the affected versions and implement parameterized queries/input validation to prevent SQL injection. Educate users about social engineering risks to prevent accidental file creation.
IBM App Connect Enterprise 12.0.12.27+ or 13.0.8.0+
- 1. Identify the currently installed IBM App Connect Enterprise or Integration Bus version
- 2. For App Connect Enterprise 12.x: Plan upgrade to version 12.0.12.27 or later
- 3. For App Connect Enterprise 13.x: Plan upgrade to version 13.0.8.0 or later
- 4. For Integration Bus 10.1.0.x: This product version is end-of-life; contact IBM for extended support options or migrate to App Connect Enterprise
- 5. Before upgrading, review IBM's migration and upgrade documentation
- 6. Perform upgrade in a test environment first
- 7. After upgrade, verify the SQL injection/file creation vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3602 — 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-2026-3602 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