In versions below 2.1.9 of the AWS IAM app for Splunk SOAR, a user who holds a role with permission to run actions
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.1.9 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.1.9
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade AWS IAM app for Splunk SOAR to 2.1.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkAWS IAM app for Splunk SOAR | Affected
| Fixed in
|
AI-suggested
A fix is available in version 2.1.9 of the AWS IAM app for Splunk SOAR, which properly masks the credentials parameter to prevent cleartext exposure. Users should upgrade to version 2.1.9 or later to remediate this vulnerability. No other mitigations are indicated or necessary if the upgrade is applied.
Description
In versions below 2.1.9 of the AWS IAM app for Splunk SOAR, a vulnerability exists where a user with permission to run actions can expose sensitive AWS credentials. This occurs because the credentials parameter in certain actions is not masked and is displayed in cleartext in the user interface. The root cause is that the app does not mark this parameter as a password, leading to potential information disclosure.