What is CVE-2026-13107?

CVE-2026-13107 is Multiple secuirty vulnerabilies addressed with IBM Business Automation Workflow August 2026. The supplied enrichment data classifies it as Injection mapped to CWE-611 XML External Entity Reference.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Exploitation is reported, but no independent confirmation is available in the sources we have. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-13107 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

5 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, database audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-13107 using CVSS 7.1, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highInjectionpublic exploit

CVE-2026-13107

CVE-2026-13107 — Multiple secuirty vulnerabilies addressed with IBM Business Automation Workflow August 2026

IBM Business Automation Workflow containers and traditional may use programming model artifacts that are vulnerable to XML Entity Injection attacks by default.

Published Sep 14, 2026Updated Sep 14, 2026Sources: IBM (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Reported

not confirmed by CISA

EPSS

ahead of 0% of scored CVEs

Affects

IBM

4 products listed

CVSS base

7.1

high

Remediation

The vendor's own words where we have them.

IBM strongly recommends addressing the vulnerability now. Affected Product(s)Version(s)Remediation / FixIBM Business Automation Workflow containersV26.0.0 - V26.0.0-IF001Apply container 26.0.0-IF002 https://www.ibm.com/support/pages/readme-ibm-business-automation-workflow-containers-26000-interim-fixes IBM Business Automation Workflow traditionalV26.0.0 - V26.0.0-IF001Apply traditional 26.0.0-IF002 https://www.ibm.com/support/pages/readme-ibm-business-automation-workflow-26000-interim-fixes IBM Business Automation Workflow containersV25.0.0 - V25.0.0-IF005Apply container 25.0.0-IF006 https://…

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
IBM	Business Automation Workflow containers and traditional	26.0.0 to <= 26.0.0 Interim Fix 001	Vulnerable
IBM	Business Automation Workflow containers and traditional	25.0.0 to <= 25.0.0 Interim Fix 005	Vulnerable
IBM	Business Automation Workflow containers and traditional	24.0.1 to <= 24.0.1 Interim Fix 008	Vulnerable
IBM	Business Automation Workflow containers and traditional	24.0.0 to <= 24.0.0 Interim Fix 009	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Low

Confidentiality

High

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.1	CVSS 3.1	high	—	—	IBM (CNA)

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-611 · Improper Restriction of XML External Entity Reference

Read Application Data
Read Files or Directories
Bypass Protection Mechanism
DoS: Resource Consumption (CPU)

Mitigation: Many XML parsers and validators can be configured to disable external entity expansion.::

Weakness & attack patterns

CWE-611XML External Entity Reference

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-221 · Data Serialization External Entities Blowup

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 5 sampled are weaponized

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Business Automation Workflow containers and traditional.
Monitor for scanner or exploit-pattern traffic after 5 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSdatabase audit logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.1 (AV:N)
Sep 14, 2026 · NVD
Initial · CVE published
Sep 14, 2026 · NVD
CVE published by MITRE.
Sep 14, 2026 · SOCRadar CTI

References

1 on the record

www.ibm.com/support/pages/node/7285930
Vendor Advisory

Elsewhere on this site

IBMevery CVE for this vendor
Injectionsame class
CWE-611other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-13107 is Multiple secuirty vulnerabilies addressed with IBM Business Automation Workflow August 2026, a high vulnerability affecting Business Automation Workflow containers and traditional from IBM. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: 5 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.1 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.