Splunk Fixes 146 Flaws Including CVSS 9.9 SOAR Code Execution Bug

Splunk's November update fixes 146 vulnerabilities across five advisories, including CVE-2026-131253, a CVSS 9.9 code execution flaw in Splunk SOAR software.
Table of Contents
    Add a header to begin generating the table of contents

    Splunk published five security advisories on November 18 that fix 146 vulnerabilities, with severity ratings reaching CVSS 9.9. The most serious, CVE-2026-131253, allows a logged-in user to run arbitrary code in Splunk SOAR, the company’s security orchestration and automation platform.

    SVD-2026-1108 Patches 59 Bugs in Splunk SOAR

    The largest share of the SOAR fixes comes from advisory SVD-2026-1108, which patches 59 bugs. CVE-2026-131253 is rated 9.9 and requires a user who already holds app and playbook rights. Those users can exploit the App Wizard, which inserts user-supplied names into connector code without checking them, and so execute arbitrary code.

    CVE-2026-131287 and the Reused Repository Name Attack

    CVE-2026-131287 carries a 9.6 score and lets an attacker run rogue playbook code when the name of a deleted repository is reused. In that scenario, a repository that was removed and later recreated under the same name could cause the platform to run code that an attacker controls.

    The flaw illustrates how identity assumptions in automation platforms can be turned against them, since the system treats a recreated name as the same trusted source as before.

    Both SOAR flaws involve user-controlled names flowing into code that the platform later runs. In CVE-2026-131253 the App Wizard places a user-supplied name into connector code without validating it, and in CVE-2026-131287 a repository name is trusted after reuse. The common thread is that the platform builds executable content from names an attacker can choose.

    Splunk Enterprise Advisory Includes Two Critical Login-Bypass Bugs

    Advisory SVD-2026-1103 fixes 38 flaws in Splunk Enterprise. Two of them are critical login-bypass bugs, among them CVE-2026-76536, rated 9.4 and affecting standalone hosts. A login bypass in a platform that stores logs removes the authentication barrier in front of the data the system holds.

    Remaining Advisories Account for the Rest of the 146 Fixes

    The two named advisories cover 97 of the 146 fixes. The remaining 49 are spread across three further advisories, covering Splunk Enterprise and related apps. Public detail on those three is limited.

    No Exploitation Reported, but the Target Is Valuable

    Splunk has not reported active exploitation, and no public exploit code has surfaced. Splunk is used by more than 15,000 firms in 110 countries, according to a report on the update.

    The target makes the update important regardless of exploitation status. Security-operations platforms hold logs and response playbooks, so compromise could affect an organization’s ability to detect and respond to incidents. An attacker with code execution in SOAR could alter or abuse the playbooks that automate containment actions, which would turn a defensive tool into a vector.

    Why the SOAR Rights Requirement Limits but Does Not Remove Risk

    CVE-2026-131253 needs an authenticated user with app and playbook rights, which restricts the pool of possible attackers compared with an unauthenticated flaw. Even so, accounts with those rights typically belong to security engineers and automation developers, and credentials for such accounts are worth stealing for the access they would give.

    The two login-bypass bugs in Splunk Enterprise carry a different profile because they target authentication itself, and the standalone-host condition on CVE-2026-76536 means the exposure depends on how a given deployment is arranged.

    Splunk’s 146 Fixes as a Burden for Security Teams

    A 146-fix release is a large patching task for a team that runs several Splunk components, and the SOAR advisory alone accounts for 59 of them while the Enterprise advisory accounts for 38 more. Splunk’s guidance is to apply the November patches. The volume of fixes, and the number of distinct advisories, means administrators must match each advisory to the components they actually operate before they can set priorities.

    Related Posts