CVE-2026-76383: In versions below 1.0.5 of the RSA SecurID Authentication Manager app for Splunk SOAR, a user who holds a role with permission to run actions could
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 1.0.5 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.5
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 RSA SecurID Authentication Manager app for Splunk SOAR to 1.0.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkRSA SecurID Authentication Manager app for Splunk SOAR | Affected
| Fixed in
|
AI-suggested
A fix is available in version 1.0.5 of the RSA SecurID Authentication Manager app for Splunk SOAR. Users should upgrade to version 1.0.5 or later to ensure the token_serial parameter is properly masked. Until upgraded, restrict permissions to run actions to trusted users only to minimize exposure.
Description
Versions of the RSA SecurID Authentication Manager app for Splunk SOAR below 1.0.5 contain an information disclosure vulnerability. A user with permission to run actions can see sensitive token serials in cleartext when invoking enable or revoke token actions because the token_serial parameter is not masked in the user interface. This occurs because the app does not treat this parameter as a password. The vulnerability has a CVSS score of 4.3, indicating medium severity.