Skip to content
major vulnerability· requires attention

Critical SSRF in widely used IBM API Connect allowing internal access, data exposure and bypass of API controls; enterprise-impacting API management product.

Applications

CVE-2026-17353

9.6
Critical
EPSS n/aPatch available

Authenticated SSRF in IBM API Connect permits internal access and data exposure.

exploited
No known exploitation not in CISA KEV as of our last sync
fix
Patch available see the advisory in the references
likelihood
No EPSS score yet
Published 7 Nov 2026Analysed here 8 Nov 2026CVSS scored by the publisher (CNA)
common questions

Is CVE-2026-17353 being exploited?

Not confirmed. CVE-2026-17353 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-17353?

CVE-2026-17353 is rated Critical with a CVSS score of 9.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-17353?

Yes. A fix has been recorded for CVE-2026-17353. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-17353 affect?

CVE-2026-17353 affects IBM API Connect 12.1.0.0 - 12.1.1.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-17353?

Apply IBM patch immediately; restrict access, rotate creds, and review API logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
IBM API Connect 12.1.0.0 - 12.1.1.2
impact

Authenticated SSRF lets attackers access internal resources, exfiltrate sensitive data, and bypass API access controls.

action required

Immediate action required

affected versions
IBM API Connect
  • affected>= 12.1.0.0 and <= 12.1.1.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

timeline

  1. 7 Nov 2026Published
  2. 7 Nov 2026CVE record last updated · same day later
  3. 8 Nov 2026Analysed by vulneraibility.com · 1 day later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
1 reference in the CVE record: 1 patch
  • Patchibm.com /support/pages/node/7295635

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved