CVE-2026-18838

CVE-2026-18838 is a critical-severity vulnerability in Ibm Api Connect with a CVSS 3.x base score of 9.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-290.

Key facts

Description

IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information and modify API configurations due to improper authentication. Identity information supplied in requests is not sufficiently verified, which could allow a caller to impersonate another user.

Frequently asked questions

What is CVE-2026-18838?
IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information and modify API configurations due to improper authentication. Identity information supplied in requests is not sufficiently verified, which could allow a caller to impersonate another user.
How severe is CVE-2026-18838?
CVE-2026-18838 has a CVSS 3.x base score of 9.4, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability low.
Is CVE-2026-18838 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-18838?
CVE-2026-18838 affects Ibm Api Connect. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-18838?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-18838 published?
CVE-2026-18838 was published on 2026-11-07 and last updated on 2026-11-16.

References

Affected products (1)

More vulnerabilities in Ibm Api Connect

All CVEs affecting Ibm Api Connect →

Other CWE-290 vulnerabilities

Browse all CWE-290 vulnerabilities →