MEDIUM 4.7

CVE-2026-3602: IBM App Connect Enterprise SQL Injection & File Manipulation Vulnerability

IBM App Connect Enterprise and Integration Bus contain a SQL injection vulnerability that could allow a remote attacker to trick users into inadvertently creating files on their systems. While the attack requires user interaction and operates with local system access constraints, successful exploitation could result in unauthorized file creation or modification. The vulnerability affects multiple versions across IBM's integration middleware stack.

Source data · NVD / CISA · public domain

CVSS
3.1 · 4.7 MEDIUM · CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
Weaknesses (CWE)
CWE-73, CWE-89
Affected products
3 configuration(s)
Published / Modified
2026-06-30 / 2026-07-20

NVD description (verbatim)

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

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

This vulnerability stems from improper input validation in SQL query construction within IBM App Connect Enterprise versions 13.0.1.0–13.0.7.2 and 12.0.1.0–12.0.12.26, as well as IBM Integration Bus for z/OS versions 10.1.0.0–10.1.0.7. The flaw combines SQL injection (CWE-89) with improper file handling (CWE-73), enabling an attacker to manipulate SQL statements and potentially control file operations. Exploitation requires social engineering to induce a user to perform an action—such as opening a crafted file or clicking a malicious link—that triggers the vulnerable code path.

Business impact

The primary risk is integrity compromise: attackers could create or modify files in locations accessible to the compromised application process, potentially planting malicious content, altering configuration files, or disrupting service availability. For organizations running IBM integration infrastructure in production, this represents a supply-chain and data-integrity concern, particularly if Integration Bus instances handle sensitive data transformations or message routing. Remediation requires patching and user awareness training to reduce social engineering success rates.

Affected systems

Vulnerable products include: IBM App Connect Enterprise (versions 13.0.1.0 through 13.0.7.2, and 12.0.1.0 through 12.0.12.26); IBM Integration Bus for z/OS (versions 10.1.0.0 through 10.1.0.7). Organizations should inventory deployments of these products and cross-reference against their internal version control to identify exposure.

Exploitability

Exploitation requires two conditions: the attacker must craft a malicious input (likely embedded in a file or message), and a user must be socially engineered into triggering it. The local attack vector and requirement for user interaction elevate the barrier to opportunistic mass exploitation, making this a targeted or campaign-specific threat rather than a wormable vulnerability. However, in environments with high-volume file processing or messaging, the attack surface may be broader.

Remediation

Apply vendor patches for all affected versions as soon as available. For IBM App Connect Enterprise, update to a patched version above 13.0.7.2 or 12.0.12.26. For IBM Integration Bus for z/OS, update to a version above 10.1.0.7. Verify patch availability and compatibility with your deployment configuration through IBM support channels. Until patching is complete, enforce user awareness training on opening untrusted files and restrict user permissions to the minimum necessary for operational tasks.

Patch guidance

Contact IBM support or consult the IBM security advisories for your specific product line to confirm available patch versions and migration paths. Verify compatibility of patches with dependent applications and z/OS subsystems before applying. Schedule patching during maintenance windows to minimize integration service disruption. Test patches in non-production environments first to validate functionality.

Detection guidance

Monitor application logs for unusual SQL queries containing special characters or suspicious syntax patterns. Track file creation and modification events in directories accessible to App Connect Enterprise and Integration Bus processes. Implement file integrity monitoring (FIM) on configuration and data directories. Use security information and event management (SIEM) tools to correlate user authentication events with subsequent file-creation activity to identify potential social engineering incidents.

Why prioritize this

Although the CVSS score of 4.7 (MEDIUM) reflects the need for user interaction and local constraints, organizations should prioritize remediation based on whether they run these products in critical integration workflows. The combination of SQL injection and file manipulation in middleware that processes enterprise data justifies elevated attention in integration-centric architectures.

Risk score, explained

The CVSS 3.1 score of 4.7 reflects a Medium severity rating driven by: local attack vector (AV:L), high complexity (AC:H), no privileges required, user interaction mandatory (UI:R), and high impact to integrity (I:H). The score correctly discounts the severity due to the social engineering requirement and local scope, but does not capture business context—organizations heavily dependent on IBM integration infrastructure should apply additional weight in their risk frameworks.

Frequently asked questions

Do I need to patch immediately if I'm on a non-vulnerable version?

No. Verify your exact version against the vulnerable ranges (13.0.1.0–13.0.7.2 and 12.0.1.0–12.0.12.26 for App Connect Enterprise; 10.1.0.0–10.1.0.7 for Integration Bus z/OS). If you're on a version outside these ranges, you are not affected by this specific vulnerability.

What's the difference between this vulnerability and a typical SQL injection?

This vulnerability combines SQL injection with file manipulation (CWE-73), meaning the attacker's payload can influence both database queries and file system operations. The social engineering component is also critical—an attacker must trick a user into triggering the malicious code, rather than exploiting it remotely without user action.

Will my existing Web Application Firewall (WAF) rules catch this?

Standard SQL injection WAF rules may detect some payloads, but this vulnerability's tight coupling with file operations and reliance on user interaction means a WAF alone is insufficient. Deploy defense in depth: WAF rules, input validation at the application level, file integrity monitoring, and user security awareness training.

Is this vulnerability tracked in CISA's Known Exploited Vulnerabilities catalog?

No, this vulnerability is not currently on the CISA KEV list, indicating no widespread active exploitation has been reported as of the last update. However, absence from the list does not guarantee the vulnerability remains unexploited—monitor threat intelligence feeds and vendor advisories for any changes.

This analysis is provided for informational purposes and reflects information available as of the publication date. Patch availability, version numbers, and migration guidance should be verified directly against IBM's official security advisories and support documentation. SEC.co assumes no liability for inaccuracies in vendor guidance or outcomes of remediation efforts. Organizations should conduct their own risk assessment and testing before applying patches to production environments. Source: NVD (public-domain), retrieved 2026-08-09. Analysis generated by SEC.co (claude-haiku-4-5).