CVE-2026-17335 · Vendor
NO FIX YET · SEE WHAT TO DO
IBM API Connect versions 12.1.0.0 through 12.1.1.2 do not validate file paths in uploaded content, so files can be written outside the intended directory. An authenticated remote attacker can use this to get code executed on the server.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Organizations running IBM API Connect 12.1.0.0 through 12.1.1.2 where users can upload content. The attacker needs a valid account on the platform. The sources do not say which upload features or configurations are required, so teams on those versions should treat themselves as exposed until they confirm otherwise.
Not affected if versions-outside-range
Who cares api-gateway, ibm-api-connect, self-hosted
12.1.0.0 through 12.1.1.212.1.1.2; the sources do not name the exact fixed versionIBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to execute arbitrary code due to path traversal. File paths in uploaded content are not sufficiently validated, which could allow files to be written outside the intended location and code to be executed.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.