Skip to main content
CVE-2026-76378VulnerabilityPublished

In versions below 2.4.5 of the Cisco Secure Malware Analytics app for Splunk SOAR, a user who holds a role with

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76378· Medium 4.3

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

Data as of 16 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.4.5
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 16 Nov 2026.

What to do

Upgrade Cisco Secure Malware Analytics app for Splunk SOAR to 2.4.5.

Affected software

ProductAffectedFixed in
SplunkCisco Secure Malware Analytics app for Splunk SOARAffected
  • >=2.4 <2.4.5
Fixed in
  • 2.4.5

AI-suggested

Upgrade to version 2.4.5 or later of the Cisco Secure Malware Analytics app for Splunk SOAR where this issue is fixed. Patch status is not explicitly confirmed in the provided data, but the version boundary indicates the fix is in 2.4.5. Until upgrading, restrict roles with permission to run actions to trusted users only.

Description

In versions below 2.4.5 of the Cisco Secure Malware Analytics app for Splunk SOAR, a user with permission to run actions could see a sensitive sample password in cleartext when invoking the detonate file action. This occurs because the sample_password parameter is not masked in the user interface, leading to information disclosure. The issue arises from the app not marking this parameter as a password.

References

Community reviews

Loading reviews…