Y2Y2
Explore more on Y2
Public vulnerability disclosure
Investigate in Cyber
Open

CVE-2026-108178

Multiple Vulnerabilities in IBM API Connect

publishedCWE-358

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a token to be accepted that should be rejected due to an improperly implemented security check. Under certain conditions, token validation is incomplete, so a token may be accepted for a purpose it was not intended for.

Technical severity4.2 mediumCVSS 3.1 · CNA: ibm
Published2026-11-07Source updated 2026-11-11
Collected2026-11-113 attributed sources

Fixes and workarounds

Fix

IBM strongly recommends addressing the vulnerability now by upgrading to v12.1.1.3 Fix Central Link: https://www.ibm.com/support/pages/node/7290205 IBM strongly recommends addressing the vulnerability now by upgrading to 10.0.8.13Fix Central Link: https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=10.0.8.12&platform=All&function=all

Source: CNA: ibm

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: CNA: ibm

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: CNA: ibm

Affected products and versions

ProductVersionsAuthority
API Connect
IBM 		≥ 12.1.0.0; ≤ 12.1.1.2 (affected, semver)
≥ 10.0.8.0; ≤ 10.0.8.12 (affected, semver) 		CNA: ibm

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

NVD applicability configurations (1)

These expressions retain AND/OR operators, negation, and required environmental products. A listed product is not sufficient to establish exposure when additional conditions apply.

[
  {
    "negate": false,
    "nodes": [
      {
        "cpeMatch": [
          {
            "criteria": "cpe:2.3:a:ibm:api_connect:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "10.0.8.13",
            "versionStartIncluding": "10.0.8.0",
            "vulnerable": true
          },
          {
            "criteria": "cpe:2.3:a:ibm:api_connect:*:*:*:*:*:*:*:*",
            "versionEndExcluding": "12.1.1.3",
            "versionStartIncluding": "12.1.0.0",
            "vulnerable": true
          }
        ],
        "negate": false,
        "operator": "OR"
      }
    ],
    "operator": "OR"
  }
]

CVSS assessments

Version / scoreVectorAuthority
3.1 / 4.2
medium		 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:NCNA: ibm
3.1 / 4.2
medium		 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:NNVD: [email protected]

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Get an API keyUse x402Connect an agent
Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide