On this page (8 sections)
IBM API Connect versions 12.1.0.0 through 12.1.1.2 contain a server-side request forgery (SSRF) weakness, tracked as CVE-2026-17344. According to the NVD record, a remote attacker could use it to obtain sensitive information, because a service that can be reached without authentication could be made to send requests to unintended destinations.
If you run IBM API Connect 12.1.0.0 through 12.1.1.2, or host it for clients, treat this as a priority item. The details below are limited to what the public record states, and we flag what is not yet known.
At a glance
What happened
The CVE was published on 2026-11-07 and references an IBM support page, IBM node 7295635, as its vendor reference. The NVD description says a service that can be reached without authentication could be made to send requests to destinations the operator never intended. The stated impact is disclosure of sensitive information.
Only one independent publisher covers this story so far, and the research available to us contains the CVE description, the score and the IBM reference link. It does not include the text of IBM's advisory. We therefore cannot tell you the fixed version, any interim fix, or whether attacks have been seen. Read IBM's page directly for those details.
How this kind of flaw works
Server-side request forgery means an attacker persuades a server to make a network request on their behalf. The attacker does not need to reach the target directly. The vulnerable server does it for them, from a position the network often trusts.
That matters because servers typically sit in places that outsiders cannot reach: internal admin interfaces, other services in the same cluster, and cloud metadata endpoints that can hand out credentials. When an SSRF flaw sits in a service that needs no login, the barrier to trying it is low. The NVD entry describes information disclosure as the result, which fits the common pattern of reading responses from internal resources.
The research does not include the CVSS vector or say which organization assigned the 9.3 score, so we do not break the score down further.
Who is exposed
- Teams running IBM API Connect at any version from 12.1.0.0 up to and including 12.1.1.2.
- Organizations where an API Connect service is reachable from the internet or from a large, loosely controlled internal network.
- Hosting providers and agencies that operate API Connect on behalf of customers.
- Environments where the API Connect hosts can reach internal services or cloud metadata addresses, since those are the usual targets of SSRF.
Releases outside the 12.1.0.0 to 12.1.1.2 range are not named in the record. Do not assume other branches are unaffected without checking IBM's page.
If you operate API Connect, also check IBM's advisories for any other issues affecting your version, and see our security news and analysis for related coverage of the product.
How to check your exposure
- Find every API Connect deployment you own, including test, staging and customer-hosted ones.
- Record the installed version of each and compare it with the affected range, 12.1.0.0 through 12.1.1.2.
- Open the IBM advisory at the reference link above and confirm the remediation it lists for your version.
- Map which API Connect services are reachable without authentication, and from where (internet, partner networks, internal only).
- Review what those hosts can reach on the internal network, so you know the potential impact if a request were misdirected.
What to do now
- Inventory all API Connect instances and note any on 12.1.0.0 through 12.1.1.2.
- Read IBM's advisory and apply the fix or mitigation it specifies for your release.
- Until patched, restrict network access to the unauthenticated services so only required clients can reach them.
- Limit outbound connections from API Connect hosts to the destinations they actually need.
- Block access from these hosts to cloud metadata endpoints and sensitive internal ranges where your design allows it.
- Review credentials and secrets that these hosts could reach, and rotate them if you see signs of misuse.
- Check access and egress logs for unusual outbound requests, then document the review.
Detection and monitoring
SSRF attempts tend to show up as requests from your server to addresses it normally never contacts. Watch egress logs and firewall logs from API Connect hosts for connections to internal ranges, link-local addresses or unfamiliar external hosts. Unexpected spikes in requests to the unauthenticated service are also worth a look.
From the outside, you can keep an eye on what your public endpoints expose. Webforta's security scanner runs read-only checks on sites you verify, and monitoring can alert you to certificate, DNS and header changes. Neither confirms or rules out this specific flaw, so version checks against IBM's advisory remain the deciding step.
If you suspect misuse, our guides on checking whether a website is hacked and what to do after a compromise cover the first response.
Timeline
- 2026-11-07: CVE-2026-17344 is published, with CVSS 9.3 and a reference to IBM's support page.
- Not yet confirmed in our sources: the fixed version, any interim mitigation, and whether the flaw is being exploited. Check IBM's advisory for current guidance.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
