dbcve.org
Api ConnectApplication · Ibm

CVE-2026-9074

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 10.0.8.10 / 12.1.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

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 · unedited
IBM API Connect 10.0.8.0 through 10.0.8.9 and 12.1.0.0 through 12.1.0.3 contains an unauthenticated SQL injection vulnerability in the password reset functionality.

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 confidence

IBM API Connect versions 10.0.8.0-10.0.8.9 and 12.1.0.0-12.1.0.3 contain an unauthenticated SQL injection vulnerability in the password reset functionality. An attacker can exploit this without credentials to inject malicious SQL queries, potentially allowing unauthorized database access, data exfiltration, or system compromise.

MitigationApply the vendor-supplied patch or upgrade to a fixed version of IBM API Connect beyond the affected version ranges.

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
Api ConnectApplication
Affected:>= 10.0.8.0, < 10.0.8.10>= 12.1.0.0, < 12.1.1.0

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IBM API Connect version
    Run the command to retrieve the API Connect version (typically via 'apic status' or checking the product UI/management console)
    Affected if The version number is 10.0.8.0 through 10.0.8.9, or 12.1.0.0 through 12.1.0.3 (or any version below 10.0.8.10 or 12.1.1.0 in those branches)
  2. Verify password reset endpoint is accessible
    Confirm that the password reset functionality is enabled and reachable on your API Connect deployment (check via management UI or API documentation endpoints)
    Affected if The password reset endpoint is exposed and accessible without authentication from the network
  3. Review password reset logs for SQL errors
    Examine application and database logs for entries related to password reset requests that contain SQL syntax errors, unusual database warnings, or exception messages indicating SQL injection attempts
    Affected if Unexpected SQL syntax errors or injection patterns appear in logs associated with password reset operations
  4. Check for unauthorized database modifications
    Audit database tables, especially user records, for unexpected changes or new accounts that were not created through normal administrative processes
    Affected if Any unauthorized modifications exist in user or authentication-related tables

You are affected if your IBM API Connect version falls within 10.0.8.0-10.0.8.9 or 12.1.0.0-12.1.0.3 and the password reset endpoint is network-accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 10.0.8.10 / 12.1.1.0 or later
Fixed in 10.0.8.1012.1.1.0
Interim mitigation

Apply the vendor-supplied patch or upgrade to a fixed version of IBM API Connect beyond the affected version ranges.

Recommended fix Moderate confidence

Upgrade to IBM API Connect 10.0.8.10 or later, or 12.1.1.0 or later depending on your current major version line

  1. Review IBM API Connect upgrade documentation for your current version
  2. Ensure you have a complete backup of your current configuration and data
  3. Schedule a maintenance window for the upgrade process
  4. Download the appropriate fixed version (10.0.8.10 or later for 10.0.x line, 12.1.1.0 or later for 12.1.x line) from IBM Fix Central
  5. Follow IBM's standard upgrade procedure for API Connect (typically via the apic command-line tool or management console)
  6. After upgrade, verify the password reset functionality is working correctly
  7. Confirm the SQL injection vulnerability is resolved by checking the fixed version is running
Caveat IBM API Connect upgrades may require configuration adjustments; review release notes for breaking changes between versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Api Connect Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9074 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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