Security
CVE-2026-19124: IBM API Connect 10.0.8.0 through 10.0.8.12 uses hard-coded key protecting stored credentials
A published CVE reports that IBM API Connect versions 10.0.8.0 through 10.0.8.12 protect stored credentials with a cryptographic key built into the product, so an attacker who obtains the stored data could decrypt them. The entry rates the issue CVSS 3.1 MEDIUM and maps it to CWE-798.
A vulnerability entry published on November 7, 2026 describes CVE-2026-19124, which affects IBM API Connect 10.0.8.0 through 10.0.8.12. According to the description, the product "could allow an attacker with access to stored data to decrypt sensitive credentials due to the use of a hard-coded cryptographic key." The entry adds that "The key protecting stored credentials is built into the product, so credentials could be decrypted if the stored data is obtained."
The entry lists the issue as remotely exploitable and records CVSS 3.1 scores of MEDIUM, attributed to MITRE-CVE among other sources. It associates the vulnerability with CWE-798, the weakness class for use of hard-coded credentials, and links to an IBM support page as a reference. The entry was last modified on November 8, 2026, when an SSVC record was added with the options exploitation "none", automatable "no" and technicalImpact "partial".
The listed solution is to "Update the product to a secure version," alongside implementing "proper key management practices" and rotating cryptographic keys regularly. The entry does not state which release contains the fix.
Analysis: For teams building AI agents, the practical question is where the key-encryption key for stored tool credentials actually comes from, and whether it can be rotated without waiting on a vendor release.
Claims and evidence
What the author claims, and what backs it up. Key claims are the ones the story depends on.
-
CVE-2026-19124 affects IBM API Connect 10.0.8.0 through 10.0.8.12.
Key claim
Supported
-
quote
https://cvefeed.io/vuln/detail/CVE-2026-19124“IBM API Connect 10.0.8.0 through 10.0.8.12 could allow an attacker with access to stored data to decrypt sensitive credentials due to the use of a hard-coded cryptographic key.”
-
quote
-
The key protecting stored credentials is built into the product, so credentials could be decrypted if the stored data is obtained.
Key claim
Supported
-
quote
https://cvefeed.io/vuln/detail/CVE-2026-19124“The key protecting stored credentials is built into the product, so credentials could be decrypted if the stored data is obtained.”
-
quote
-
The vulnerability entry was published on November 7, 2026.
Key claim
Partial
-
quote
https://cvefeed.io/vuln/detail/CVE-2026-19124“Published Date: Nov. 7, 2026, 5:19 a.m.”
-
quote
-
The entry was last modified on November 8, 2026.
Key claim
Partial
-
quote
https://cvefeed.io/vuln/detail/CVE-2026-19124“Last Modified: Nov. 8, 2026, 2:17 a.m.”
-
quote
-
The entry lists the issue as remotely exploitable.
Key claim
Partial
-
quote
https://cvefeed.io/vuln/detail/CVE-2026-19124“Remotely Exploit: Yes !”
-
quote
-
The entry records CVSS 3.1 scores of MEDIUM.
Key claim
Partial
-
quote
https://cvefeed.io/vuln/detail/CVE-2026-19124“CVSS 3.1 | MEDIUM”
-
quote
-
The entry associates the vulnerability with CWE-798.
Key claim
Supported
-
quote
https://cvefeed.io/vuln/detail/CVE-2026-19124“CVE-2026-19124 is associated with the following CWEs:”
-
quote
-
The listed solution includes updating the product to a secure version.
Key claim
Supported
-
quote
https://cvefeed.io/vuln/detail/CVE-2026-19124“Update the product to a secure version.”
-
quote