Skip to main content
VulnerabilityPublished

CVE-2026-76379: Cisco Webex app for Splunk SOAR · The application stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

Affects Cisco Webex app for Splunk SOARSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.2.1 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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.2.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Upgrade Cisco Webex app for Splunk SOAR to 2.2.1.

Affected software

ProductAffectedFixed in
SplunkCisco Webex app for Splunk SOARAffected
  • >=2.2 <2.2.1
Fixed in
  • 2.2.1

AI-suggested

Upgrade to version 2.2.1 or later of the Cisco Webex app for Splunk SOAR, where this issue is fixed by masking the password parameter. Since the vulnerability is addressed in 2.2.1, applying this official fix is the recommended remediation.

Description

CVE-2026-76379 affects the Cisco Webex app for Splunk SOAR versions 2.2 and 2.2.x prior to 2.2.1. The vulnerability allows users with permission to run actions to see sensitive meeting passwords in cleartext when using the schedule meeting action. This occurs because the password parameter is not masked in the user interface, leading to potential information disclosure.

References

Community reviews

Loading reviews…