Act nowDisclosed

Advisory · CVE-2026-16884

IBM API Connect XML external entity injection exposes sensitive information

IBM API Connect 12.1.0.0 through 12.1.1.2 lets a remote attacker obtain sensitive information through an XML external entity injection, rated critical at CVSS 9.9.

Advisory published November 7, 2026Independent summary
Vendor
IBM
Product
API Connect
Identifier / CWE
CVE-2026-16884
CWE-611
Action timing
Immediate
ELI5

Explain it like I’m five

API Connect reads XML documents but follows instructions hidden inside them. An attacker can slip in an instruction that says fetch this private file, and the server obeys and hands the contents back.

SIMPLIFIED_ATTACK_PATH04 STEPS
  1. 01Malicious XML submitted

    A remote attacker sends an XML document containing an external entity definition to API Connect 12.1.0.0 through 12.1.1.2.

  2. 02Entity resolved by parser

    The XML parser resolves the external entity instead of treating it as inert text.

  3. 03Internal content read

    The entity points at local files or internal services, whose contents are read by the server.

  4. 04Sensitive data returned

    The attacker obtains sensitive information in the response.

What happened

IBM disclosed CVE-2026-16884 as part of a multi-vulnerability API Connect bulletin: API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information due to an XML external entity injection. The record rates it critical at CVSS 9.9 under version 3.1, with network attack vector, low complexity, no privileges required, and changed scope.

This is one of about 98 CVEs in the same IBM API Connect bulletin; this advisory covers only this CVE. The bulletin text read for this run does not state a fixed release version, so none is claimed here. XXE in an API gateway is a path to the files and services behind it, which is why the score reaches 9.9 despite the impact being information disclosure.

What to do

  1. Inventory IBM API Connect deployments and record each version, including management, gateway, and analytics components.
  2. Apply the fix from IBM’s security bulletin for the affected release lines.
  3. Until patched, restrict network access to the API Connect management and gateway interfaces and treat them as untrusted-input surfaces.
  4. Review access and audit logs for token use by unexpected users, unexpected administrative operations, and requests to internal or metadata addresses.
  5. Rotate API keys, tokens, and credentials if misuse or unauthorized access cannot be excluded.
  6. Verify the deployed version after updating.

Management note

An API gateway that reads attacker XML is a front door to everything behind it. Patch, then check what the parser may have read while the flaw was open.