CVE-2026-2606
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM webMethods API Gateway (on-prem) 10.11 through 10.11_Fix3210.15 to 10.15_Fix2711.1 to 11.1_Fix7 IBM webMethods API Management (on-prem) fails to properly validate user-supplied input passed to the url parameter on the /createapi endpoint. An attacker can modify this parameter to use a file:// URI schema instead of the expected https:// schema, enabling unauthorized arbitrary file read access on the underlying server file system.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM webMethods API Gateway fails to validate the url parameter on the /createapi endpoint, allowing attackers to supply file:// URIs instead of the expected https:// schema. This enables arbitrary file read access on the server filesystem via local file inclusion through the file protocol.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 10.11= 10.15= 11.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed API Gateway versionLocate the webMethods API Gateway installation directory and check the version file or use the product's version command/utility. Common locations include the installation root or via the webMethods Administrator console.Affected if The installed version matches 10.11, 10.15, or 11.1 exactly.
-
Confirm /createapi endpoint is exposedAttempt to access the /createapi endpoint on your API Gateway server (e.g., GET request to https://yourgateway/createapi or similar path depending on your deployment). Check if the endpoint responds.Affected if The /createapi endpoint is accessible without authentication or with valid authentication.
-
Test URL parameter validation for file:// schemeSend a POST request to the /createapi endpoint with a file:// URL parameter (e.g., url=file:///etc/passwd or url=file://C:\Windows\win.ini) and observe the response. Compare against a request using https://.Affected if The endpoint accepts file:// URIs without rejecting them or the response reveals file contents.
-
Review URL scheme allowlist configurationAccess the API Gateway administrative console or configuration files. Look for settings that control allowed URI schemes for the url parameter on API creation endpoints.Affected if No allowlist restricting schemes to https:// (or http(s) only) is found, or the configuration explicitly allows file://.
You are affected if your installed version is exactly 10.11, 10.15, or 11.1 AND the /createapi endpoint accepts file:// URIs without rejecting them.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict the url parameter to only accept https:// (or allowed http(s)) schemes via allowlist validation, rejecting all other URI schemes including file://. Apply available vendor patches for affected versions.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2606 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2606 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data