Search

Find a vulnerability

Search criteria

    25 vulnerabilities found for Splunk AI Toolkit by Splunk

    CERTFR-2026-AVI-1056

    Vulnerability from certfr_avis - Published: 2026-08-20 - Updated: 2026-08-20

    De multiples vulnérabilités ont été découvertes dans les produits Splunk. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une élévation de privilèges et une atteinte à la confidentialité des données.

    Solutions

    Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).

    Impacted products
    Vendor Product Description
    Splunk N/A MS Graph pour Active Directory app pour Splunk SOAR versions antérieures à 1.5.2
    Splunk N/A Venafi app pour Splunk SOAR versions antérieures à 2.1.4
    Splunk Universal Forwarder Splunk Universal Forwarder versions 10.0.x antérieures à 10.0.9
    Splunk N/A AWS IAM app pour Splunk SOAR versions antérieures à 2.1.9
    Splunk N/A Azure AD Graph app pour Splunk SOAR versions antérieures à 2.5.3
    Splunk SOAR Splunk SOAR versions antérieures à 8.6.0
    Splunk Splunk Splunk Connect pour Kafka versions antérieures à 2.2.7
    Splunk Splunk Enterprise Splunk Enterprise versions 9.4.x antérieures à 9.4.14
    Splunk N/A FireAMP versions 2.1.x antérieures à 2.1.15
    Splunk N/A Zoom app pour Splunk SOAR versions antérieures à 3.2.2
    Splunk N/A Phantom app pour Splunk SOAR versions antérieures à 3.8.5
    Splunk Splunk Splunk On-Call (VictorOps) versions antérieures à 1.0.43
    Splunk Splunk Splunk Attack Analyzer Connector pour Splunk SOAR versions 2.2.x antérieures à 2.2.1
    Splunk Splunk Splunk MCP Server app versions antérieures à 1.2.1
    Splunk Splunk Enterprise Splunk Enterprise versions 10.4.x antérieures à 10.4.2
    Splunk N/A AD LDAP app pour Splunk SOAR versions antérieures à 2.3.8
    Splunk Splunk Enterprise Splunk Enterprise versions 10.2.x antérieures à 10.2.6
    Splunk Universal Forwarder Splunk Universal Forwarder versions 9.4.x antérieures à 9.4.14
    Splunk Splunk AI Toolkit Splunk AI Toolkit versions antérieures à 6.0.1
    Splunk Universal Forwarder Splunk Universal Forwarder versions 10.2.x antérieures à 10.2.6
    Splunk N/A Cisco Talos Intelligence pour Enterprise Security Cloud versions antérieures à 1.0.3
    Splunk Splunk Enterprise Splunk Enterprise versions 10.0.x antérieures à 10.0.9
    Splunk N/A CrowdStrike OAuth API app pour Splunk SOAR versions antérieures à 5.1.3
    Splunk Enterprise Security Splunk Enterprise Security versions antérieures à 8.6.1
    Splunk N/A Nmap Scanner versions 3.0.x antérieures à 3.0.15
    Splunk N/A RSA SecurID Authentication Manager app pour Splunk SOAR versions antérieures à 1.0.5
    Splunk N/A Cisco Secure Malware Analytics app pour Splunk SOAR versions antérieures à 2.4.5
    Splunk N/A Cisco Webex app pour Splunk SOAR versions antérieures à 2.2.1
    Splunk Universal Forwarder Splunk Universal Forwarder versions 10.4.x antérieures à 10.4.2
    References

    Show details on source website

    {
      "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
      "affected_systems": [
        {
          "description": "MS Graph pour Active Directory app pour Splunk SOAR versions ant\u00e9rieures \u00e0 1.5.2",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Venafi app pour Splunk SOAR versions ant\u00e9rieures \u00e0 2.1.4",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk Universal Forwarder versions 10.0.x ant\u00e9rieures \u00e0 10.0.9",
          "product": {
            "name": "Universal Forwarder",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "AWS IAM app pour Splunk SOAR versions ant\u00e9rieures \u00e0 2.1.9",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Azure AD Graph app pour Splunk SOAR versions ant\u00e9rieures \u00e0 2.5.3",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk SOAR versions ant\u00e9rieures \u00e0 8.6.0",
          "product": {
            "name": "SOAR",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk Connect pour Kafka versions ant\u00e9rieures \u00e0 2.2.7",
          "product": {
            "name": "Splunk",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk Enterprise versions 9.4.x ant\u00e9rieures \u00e0 9.4.14",
          "product": {
            "name": "Splunk Enterprise",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "FireAMP versions 2.1.x ant\u00e9rieures \u00e0 2.1.15",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Zoom app pour Splunk SOAR versions ant\u00e9rieures \u00e0 3.2.2",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Phantom app pour Splunk SOAR versions ant\u00e9rieures \u00e0 3.8.5",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk On-Call (VictorOps) versions ant\u00e9rieures \u00e0 1.0.43",
          "product": {
            "name": "Splunk",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk Attack Analyzer Connector pour Splunk SOAR versions 2.2.x ant\u00e9rieures \u00e0 2.2.1",
          "product": {
            "name": "Splunk",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk MCP Server app versions ant\u00e9rieures \u00e0 1.2.1",
          "product": {
            "name": "Splunk",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk Enterprise versions 10.4.x ant\u00e9rieures \u00e0 10.4.2",
          "product": {
            "name": "Splunk Enterprise",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "AD LDAP app pour Splunk SOAR versions ant\u00e9rieures \u00e0 2.3.8",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk Enterprise versions 10.2.x ant\u00e9rieures \u00e0 10.2.6",
          "product": {
            "name": "Splunk Enterprise",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk Universal Forwarder versions 9.4.x ant\u00e9rieures \u00e0 9.4.14",
          "product": {
            "name": "Universal Forwarder",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk AI Toolkit versions ant\u00e9rieures \u00e0 6.0.1",
          "product": {
            "name": "Splunk AI Toolkit",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk Universal Forwarder versions 10.2.x ant\u00e9rieures \u00e0 10.2.6",
          "product": {
            "name": "Universal Forwarder",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Cisco Talos Intelligence pour Enterprise Security Cloud versions ant\u00e9rieures \u00e0 1.0.3",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk Enterprise versions 10.0.x ant\u00e9rieures \u00e0 10.0.9",
          "product": {
            "name": "Splunk Enterprise",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "CrowdStrike OAuth API app pour Splunk SOAR versions ant\u00e9rieures \u00e0 5.1.3",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk Enterprise Security versions ant\u00e9rieures \u00e0 8.6.1",
          "product": {
            "name": "Enterprise Security",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Nmap Scanner versions 3.0.x ant\u00e9rieures \u00e0 3.0.15",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "RSA SecurID Authentication Manager app pour Splunk SOAR versions ant\u00e9rieures \u00e0 1.0.5",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Cisco Secure Malware Analytics app pour Splunk SOAR versions ant\u00e9rieures \u00e0 2.4.5",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Cisco Webex app pour Splunk SOAR versions ant\u00e9rieures \u00e0 2.2.1",
          "product": {
            "name": "N/A",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        },
        {
          "description": "Splunk Universal Forwarder versions 10.4.x ant\u00e9rieures \u00e0 10.4.2",
          "product": {
            "name": "Universal Forwarder",
            "vendor": {
              "name": "Splunk",
              "scada": false
            }
          }
        }
      ],
      "affected_systems_content": "",
      "content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
      "cves": [
        {
          "name": "CVE-2026-26007",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-26007"
        },
        {
          "name": "CVE-2025-13473",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-13473"
        },
        {
          "name": "CVE-2026-76349",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76349"
        },
        {
          "name": "CVE-2026-32597",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-32597"
        },
        {
          "name": "CVE-2026-31958",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-31958"
        },
        {
          "name": "CVE-2026-76329",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76329"
        },
        {
          "name": "CVE-2026-6474",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-6474"
        },
        {
          "name": "CVE-2026-40087",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-40087"
        },
        {
          "name": "CVE-2026-6472",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-6472"
        },
        {
          "name": "CVE-2026-34180",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-34180"
        },
        {
          "name": "CVE-2026-76345",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76345"
        },
        {
          "name": "CVE-2025-67726",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-67726"
        },
        {
          "name": "CVE-2026-76394",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76394"
        },
        {
          "name": "CVE-2026-76383",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76383"
        },
        {
          "name": "CVE-2026-33186",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-33186"
        },
        {
          "name": "CVE-2026-76401",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76401"
        },
        {
          "name": "CVE-2026-42766",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-42766"
        },
        {
          "name": "CVE-2026-76257",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76257"
        },
        {
          "name": "CVE-2026-32647",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-32647"
        },
        {
          "name": "CVE-2026-76324",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76324"
        },
        {
          "name": "CVE-2026-9076",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-9076"
        },
        {
          "name": "CVE-2026-76335",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76335"
        },
        {
          "name": "CVE-2026-76360",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76360"
        },
        {
          "name": "CVE-2026-76393",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76393"
        },
        {
          "name": "CVE-2026-76331",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76331"
        },
        {
          "name": "CVE-2026-76356",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76356"
        },
        {
          "name": "CVE-2026-6479",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-6479"
        },
        {
          "name": "CVE-2026-76262",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76262"
        },
        {
          "name": "CVE-2026-1642",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-1642"
        },
        {
          "name": "CVE-2026-27651",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-27651"
        },
        {
          "name": "CVE-2026-27654",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-27654"
        },
        {
          "name": "CVE-2026-76358",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76358"
        },
        {
          "name": "CVE-2026-1285",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-1285"
        },
        {
          "name": "CVE-2026-76320",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76320"
        },
        {
          "name": "CVE-2026-27959",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-27959"
        },
        {
          "name": "CVE-2026-76342",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76342"
        },
        {
          "name": "CVE-2026-6429",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-6429"
        },
        {
          "name": "CVE-2026-40701",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-40701"
        },
        {
          "name": "CVE-2026-76402",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76402"
        },
        {
          "name": "CVE-2026-2391",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-2391"
        },
        {
          "name": "CVE-2026-76395",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76395"
        },
        {
          "name": "CVE-2026-24737",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-24737"
        },
        {
          "name": "CVE-2026-27143",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-27143"
        },
        {
          "name": "CVE-2026-76369",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76369"
        },
        {
          "name": "CVE-2026-76386",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76386"
        },
        {
          "name": "CVE-2026-76344",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76344"
        },
        {
          "name": "CVE-2026-2006",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-2006"
        },
        {
          "name": "CVE-2026-42946",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-42946"
        },
        {
          "name": "CVE-2026-6637",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-6637"
        },
        {
          "name": "CVE-2026-21226",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-21226"
        },
        {
          "name": "CVE-2024-35255",
          "url": "https://www.cve.org/CVERecord?id=CVE-2024-35255"
        },
        {
          "name": "CVE-2026-76312",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76312"
        },
        {
          "name": "CVE-2026-35536",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-35536"
        },
        {
          "name": "CVE-2026-76403",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76403"
        },
        {
          "name": "CVE-2026-28755",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-28755"
        },
        {
          "name": "CVE-2026-6473",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-6473"
        },
        {
          "name": "CVE-2026-76371",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76371"
        },
        {
          "name": "CVE-2026-76313",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76313"
        },
        {
          "name": "CVE-2026-42215",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-42215"
        },
        {
          "name": "CVE-2026-2005",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-2005"
        },
        {
          "name": "CVE-2026-76327",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76327"
        },
        {
          "name": "CVE-2026-76381",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76381"
        },
        {
          "name": "CVE-2026-7383",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-7383"
        },
        {
          "name": "CVE-2026-25674",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-25674"
        },
        {
          "name": "CVE-2026-27144",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-27144"
        },
        {
          "name": "CVE-2026-76385",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76385"
        },
        {
          "name": "CVE-2026-32283",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-32283"
        },
        {
          "name": "CVE-2026-76364",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76364"
        },
        {
          "name": "CVE-2026-76388",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76388"
        },
        {
          "name": "CVE-2026-42934",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-42934"
        },
        {
          "name": "CVE-2026-24043",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-24043"
        },
        {
          "name": "CVE-2026-76261",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76261"
        },
        {
          "name": "CVE-2026-45409",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-45409"
        },
        {
          "name": "CVE-2025-53859",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-53859"
        },
        {
          "name": "CVE-2026-76378",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76378"
        },
        {
          "name": "CVE-2026-21860",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-21860"
        },
        {
          "name": "CVE-2026-4800",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-4800"
        },
        {
          "name": "CVE-2026-76354",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76354"
        },
        {
          "name": "CVE-2026-76377",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76377"
        },
        {
          "name": "CVE-2026-39883",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-39883"
        },
        {
          "name": "CVE-2026-76321",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76321"
        },
        {
          "name": "CVE-2026-0540",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-0540"
        },
        {
          "name": "CVE-2026-32281",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-32281"
        },
        {
          "name": "CVE-2025-6545",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-6545"
        },
        {
          "name": "CVE-2026-76390",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76390"
        },
        {
          "name": "CVE-2026-28389",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-28389"
        },
        {
          "name": "CVE-2026-76255",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76255"
        },
        {
          "name": "CVE-2026-33671",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-33671"
        },
        {
          "name": "CVE-2026-34515",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-34515"
        },
        {
          "name": "CVE-2026-33532",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-33532"
        },
        {
          "name": "CVE-2026-76380",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76380"
        },
        {
          "name": "CVE-2026-34519",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-34519"
        },
        {
          "name": "CVE-2026-76404",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76404"
        },
        {
          "name": "CVE-2026-76343",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76343"
        },
        {
          "name": "CVE-2026-76254",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76254"
        },
        {
          "name": "CVE-2026-30922",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-30922"
        },
        {
          "name": "CVE-2026-76397",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76397"
        },
        {
          "name": "CVE-2026-76337",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76337"
        },
        {
          "name": "CVE-2026-76326",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76326"
        },
        {
          "name": "CVE-2026-33750",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-33750"
        },
        {
          "name": "CVE-2026-76328",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76328"
        },
        {
          "name": "CVE-2026-76359",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76359"
        },
        {
          "name": "CVE-2026-76365",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76365"
        },
        {
          "name": "CVE-2026-1207",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-1207"
        },
        {
          "name": "CVE-2026-34986",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-34986"
        },
        {
          "name": "CVE-2026-33228",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-33228"
        },
        {
          "name": "CVE-2026-76405",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76405"
        },
        {
          "name": "CVE-2026-76253",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76253"
        },
        {
          "name": "CVE-2026-76314",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76314"
        },
        {
          "name": "CVE-2026-76315",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76315"
        },
        {
          "name": "CVE-2026-6638",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-6638"
        },
        {
          "name": "CVE-2026-76347",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76347"
        },
        {
          "name": "CVE-2026-34518",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-34518"
        },
        {
          "name": "CVE-2026-76382",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76382"
        },
        {
          "name": "CVE-2026-76332",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76332"
        },
        {
          "name": "CVE-2026-76379",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76379"
        },
        {
          "name": "CVE-2026-76376",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76376"
        },
        {
          "name": "CVE-2026-76252",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76252"
        },
        {
          "name": "CVE-2026-27199",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-27199"
        },
        {
          "name": "CVE-2026-76336",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76336"
        },
        {
          "name": "CVE-2026-76391",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76391"
        },
        {
          "name": "CVE-2026-22702",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-22702"
        },
        {
          "name": "CVE-2026-45447",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-45447"
        },
        {
          "name": "CVE-2026-25679",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-25679"
        },
        {
          "name": "CVE-2025-14017",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-14017"
        },
        {
          "name": "CVE-2026-76384",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76384"
        },
        {
          "name": "CVE-2026-34525",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-34525"
        },
        {
          "name": "CVE-2026-76351",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76351"
        },
        {
          "name": "CVE-2026-76256",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76256"
        },
        {
          "name": "CVE-2026-28388",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-28388"
        },
        {
          "name": "CVE-2026-76309",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76309"
        },
        {
          "name": "CVE-2026-6478",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-6478"
        },
        {
          "name": "CVE-2026-34601",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-34601"
        },
        {
          "name": "CVE-2026-24133",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-24133"
        },
        {
          "name": "CVE-2026-1312",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-1312"
        },
        {
          "name": "CVE-2026-76367",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76367"
        },
        {
          "name": "CVE-2025-14550",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-14550"
        },
        {
          "name": "CVE-2025-66221",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-66221"
        },
        {
          "name": "CVE-2026-76322",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76322"
        },
        {
          "name": "CVE-2026-76319",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76319"
        },
        {
          "name": "CVE-2026-76318",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76318"
        },
        {
          "name": "CVE-2026-2950",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-2950"
        },
        {
          "name": "CVE-2026-76258",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76258"
        },
        {
          "name": "CVE-2026-42284",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-42284"
        },
        {
          "name": "CVE-2026-6475",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-6475"
        },
        {
          "name": "CVE-2026-76370",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76370"
        },
        {
          "name": "CVE-2026-76363",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76363"
        },
        {
          "name": "CVE-2026-32280",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-32280"
        },
        {
          "name": "CVE-2026-76361",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76361"
        },
        {
          "name": "CVE-2026-76316",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76316"
        },
        {
          "name": "CVE-2026-76330",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76330"
        },
        {
          "name": "CVE-2026-76260",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76260"
        },
        {
          "name": "CVE-2025-69873",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-69873"
        },
        {
          "name": "CVE-2026-44244",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-44244"
        },
        {
          "name": "CVE-2026-25940",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-25940"
        },
        {
          "name": "CVE-2026-24040",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-24040"
        },
        {
          "name": "CVE-2026-76346",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76346"
        },
        {
          "name": "CVE-2026-76373",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76373"
        },
        {
          "name": "CVE-2026-76400",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76400"
        },
        {
          "name": "CVE-2026-76372",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76372"
        },
        {
          "name": "CVE-2026-29181",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-29181"
        },
        {
          "name": "CVE-2026-25755",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-25755"
        },
        {
          "name": "CVE-2026-76334",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76334"
        },
        {
          "name": "CVE-2025-15599",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-15599"
        },
        {
          "name": "CVE-2026-28390",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-28390"
        },
        {
          "name": "CVE-2026-6477",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-6477"
        },
        {
          "name": "CVE-2026-76340",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76340"
        },
        {
          "name": "CVE-2026-76341",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76341"
        },
        {
          "name": "CVE-2026-33672",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-33672"
        },
        {
          "name": "CVE-2026-76396",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76396"
        },
        {
          "name": "CVE-2026-76323",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76323"
        },
        {
          "name": "CVE-2026-76368",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76368"
        },
        {
          "name": "CVE-2026-76259",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76259"
        },
        {
          "name": "CVE-2026-76355",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76355"
        },
        {
          "name": "CVE-2026-76375",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76375"
        },
        {
          "name": "CVE-2026-76325",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76325"
        },
        {
          "name": "CVE-2026-76399",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76399"
        },
        {
          "name": "CVE-2026-76392",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76392"
        },
        {
          "name": "CVE-2026-34516",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-34516"
        },
        {
          "name": "CVE-2026-27140",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-27140"
        },
        {
          "name": "CVE-2026-31789",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-31789"
        },
        {
          "name": "CVE-2026-34517",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-34517"
        },
        {
          "name": "CVE-2026-25535",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-25535"
        },
        {
          "name": "CVE-2026-42945",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-42945"
        },
        {
          "name": "CVE-2026-76362",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76362"
        },
        {
          "name": "CVE-2026-76389",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76389"
        },
        {
          "name": "CVE-2026-31938",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-31938"
        },
        {
          "name": "CVE-2026-27784",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-27784"
        },
        {
          "name": "CVE-2026-76387",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76387"
        },
        {
          "name": "CVE-2026-6276",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-6276"
        },
        {
          "name": "CVE-2026-76338",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76338"
        },
        {
          "name": "CVE-2026-28753",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-28753"
        },
        {
          "name": "CVE-2026-76374",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76374"
        },
        {
          "name": "CVE-2026-33810",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-33810"
        },
        {
          "name": "CVE-2026-34513",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-34513"
        },
        {
          "name": "CVE-2026-9256",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-9256"
        },
        {
          "name": "CVE-2026-34514",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-34514"
        },
        {
          "name": "CVE-2026-28277",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-28277"
        },
        {
          "name": "CVE-2026-26996",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-26996"
        },
        {
          "name": "CVE-2026-1287",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-1287"
        },
        {
          "name": "CVE-2026-76339",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76339"
        },
        {
          "name": "CVE-2026-76348",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76348"
        },
        {
          "name": "CVE-2025-14819",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-14819"
        },
        {
          "name": "CVE-2026-76353",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76353"
        },
        {
          "name": "CVE-2025-67724",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-67724"
        },
        {
          "name": "CVE-2026-41066",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-41066"
        },
        {
          "name": "CVE-2026-76350",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76350"
        },
        {
          "name": "CVE-2026-34520",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-34520"
        },
        {
          "name": "CVE-2026-28684",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-28684"
        },
        {
          "name": "CVE-2026-32141",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-32141"
        },
        {
          "name": "CVE-2026-76357",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76357"
        },
        {
          "name": "CVE-2026-2004",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-2004"
        },
        {
          "name": "CVE-2026-76317",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76317"
        },
        {
          "name": "CVE-2026-31898",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-31898"
        },
        {
          "name": "CVE-2026-24001",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-24001"
        },
        {
          "name": "CVE-2026-76310",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76310"
        },
        {
          "name": "CVE-2026-76352",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76352"
        },
        {
          "name": "CVE-2026-25673",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-25673"
        },
        {
          "name": "CVE-2026-7168",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-7168"
        },
        {
          "name": "CVE-2025-6547",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-6547"
        },
        {
          "name": "CVE-2026-76398",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76398"
        },
        {
          "name": "CVE-2025-67725",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-67725"
        },
        {
          "name": "CVE-2026-29063",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-29063"
        },
        {
          "name": "CVE-2026-76366",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76366"
        },
        {
          "name": "CVE-2025-68428",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-68428"
        },
        {
          "name": "CVE-2026-22815",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-22815"
        },
        {
          "name": "CVE-2026-76311",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76311"
        },
        {
          "name": "CVE-2026-76263",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76263"
        },
        {
          "name": "CVE-2026-76251",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76251"
        },
        {
          "name": "CVE-2025-13465",
          "url": "https://www.cve.org/CVERecord?id=CVE-2025-13465"
        },
        {
          "name": "CVE-2026-40460",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-40460"
        },
        {
          "name": "CVE-2026-76333",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-76333"
        },
        {
          "name": "CVE-2026-44243",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-44243"
        },
        {
          "name": "CVE-2026-31790",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-31790"
        },
        {
          "name": "CVE-2026-2739",
          "url": "https://www.cve.org/CVERecord?id=CVE-2026-2739"
        }
      ],
      "initial_release_date": "2026-08-20T00:00:00",
      "last_revision_date": "2026-08-20T00:00:00",
      "links": [],
      "reference": "CERTFR-2026-AVI-1056",
      "revisions": [
        {
          "description": "Version initiale",
          "revision_date": "2026-08-20T00:00:00.000000"
        }
      ],
      "risks": [
        {
          "description": "Injection de code indirecte \u00e0 distance (XSS)"
        },
        {
          "description": "Injection de requ\u00eates ill\u00e9gitimes par rebond (CSRF)"
        },
        {
          "description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
        },
        {
          "description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
        },
        {
          "description": "Injection SQL (SQLi)"
        },
        {
          "description": "Non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur"
        },
        {
          "description": "D\u00e9ni de service"
        },
        {
          "description": "Falsification de requ\u00eates c\u00f4t\u00e9 serveur (SSRF)"
        },
        {
          "description": "Contournement de la politique de s\u00e9curit\u00e9"
        },
        {
          "description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
        },
        {
          "description": "\u00c9l\u00e9vation de privil\u00e8ges"
        }
      ],
      "summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans les produits Splunk. Certaines d\u0027entre elles permettent \u00e0 un attaquant de provoquer une ex\u00e9cution de code arbitraire \u00e0 distance, une \u00e9l\u00e9vation de privil\u00e8ges et une atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es.",
      "title": "Multiples vuln\u00e9rabilit\u00e9s dans les produits Splunk",
      "vendor_advisories": [
        {
          "published_at": "2026-08-19",
          "title": "Bulletin de s\u00e9curit\u00e9 Splunk SVD-2026-0807",
          "url": "https://advisory.splunk.com/advisories/SVD-2026-0807"
        },
        {
          "published_at": "2026-08-19",
          "title": "Bulletin de s\u00e9curit\u00e9 Splunk SVD-2026-0805",
          "url": "https://advisory.splunk.com/advisories/SVD-2026-0805"
        },
        {
          "published_at": "2026-08-19",
          "title": "Bulletin de s\u00e9curit\u00e9 Splunk SVD-2026-0803",
          "url": "https://advisory.splunk.com/advisories/SVD-2026-0803"
        },
        {
          "published_at": "2026-08-19",
          "title": "Bulletin de s\u00e9curit\u00e9 Splunk SVD-2026-0802",
          "url": "https://advisory.splunk.com/advisories/SVD-2026-0802"
        },
        {
          "published_at": "2026-08-19",
          "title": "Bulletin de s\u00e9curit\u00e9 Splunk SVD-2026-0801",
          "url": "https://advisory.splunk.com/advisories/SVD-2026-0801"
        },
        {
          "published_at": "2026-08-19",
          "title": "Bulletin de s\u00e9curit\u00e9 Splunk SVD-2026-0808",
          "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
        },
        {
          "published_at": "2026-08-19",
          "title": "Bulletin de s\u00e9curit\u00e9 Splunk SVD-2026-0806",
          "url": "https://advisory.splunk.com/advisories/SVD-2026-0806"
        },
        {
          "published_at": "2026-08-19",
          "title": "Bulletin de s\u00e9curit\u00e9 Splunk SVD-2026-0804",
          "url": "https://advisory.splunk.com/advisories/SVD-2026-0804"
        }
      ]
    }

    CVE-2026-76399 (GCVE-0-2026-76399)

    Vulnerability from nvd – Published: 2026-08-19 21:35 – Updated: 2026-08-19 21:35
    VLAI
    Title
    Incorrect Permission Assignment for Scheduled Searches in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.1, a user who holds the "power" Splunk role could modify app-provided scheduled searches to run arbitrary Search Processing Language (SPL) using the permissions of the search owner, which could allow access to all relevant data and affect system integrity. The vulnerability is possible because Splunk AI Toolkit gives the "power" Splunk role permission to modify scheduled searches that run using the permissions of the search owner.
    CWE
    • CWE-732 - The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 6.0 , < 6.0.1 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.1",
                  "status": "affected",
                  "version": "6.0",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.1, a user who holds the \"power\" Splunk role could modify app-provided scheduled searches to run arbitrary Search Processing Language (SPL) using the permissions of the search owner, which could allow access to all relevant data and affect system integrity. The vulnerability is possible because Splunk AI Toolkit gives the \"power\" Splunk role permission to modify scheduled searches that run using the permissions of the search owner."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.1, a user who holds the \"power\" Splunk role could modify app-provided scheduled searches to run arbitrary Search Processing Language (SPL) using the permissions of the search owner, which could allow access to all relevant data and affect system integrity. The vulnerability is possible because Splunk AI Toolkit gives the \"power\" Splunk role permission to modify scheduled searches that run using the permissions of the search owner."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 8.1,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-732",
                  "description": "The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:14.514Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Incorrect Permission Assignment for Scheduled Searches in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76399",
        "datePublished": "2026-08-19T21:35:14.514Z",
        "dateReserved": "2026-08-19T12:02:03.632Z",
        "dateUpdated": "2026-08-19T21:35:14.514Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76398 (GCVE-0-2026-76398)

    Vulnerability from nvd – Published: 2026-08-19 21:35 – Updated: 2026-08-20 15:26
    VLAI
    Title
    Improper Access Control during Experiment History Deletion through the REST API in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.1, a user who does not hold the "admin" or "power" Splunk roles could delete the experiment history of another user without permission through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk AI Toolkit deletes experiment history before it verifies that the user can delete the associated experiment. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-08-20 15:12 UTC
    CWE
    • CWE-862 - The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 6.0 , < 6.0.1 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-76398",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-08-20T15:12:25.499797Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-08-20T15:26:32.108Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.1",
                  "status": "affected",
                  "version": "6.0",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.1, a user who does not hold the \"admin\" or \"power\" Splunk roles could delete the experiment history of another user without permission through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk AI Toolkit deletes experiment history before it verifies that the user can delete the associated experiment. For more information see [Experiment Assistants](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.1, a user who does not hold the \"admin\" or \"power\" Splunk roles could delete the experiment history of another user without permission through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk AI Toolkit deletes experiment history before it verifies that the user can delete the associated experiment. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 4.3,
                "baseSeverity": "MEDIUM",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-862",
                  "description": "The software does not perform an authorization check when an actor attempts to access a resource or perform an action.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:13.913Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Improper Access Control during Experiment History Deletion through the REST API in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76398",
        "datePublished": "2026-08-19T21:35:13.913Z",
        "dateReserved": "2026-08-19T12:02:03.632Z",
        "dateUpdated": "2026-08-20T15:26:32.108Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76397 (GCVE-0-2026-76397)

    Vulnerability from nvd – Published: 2026-08-19 21:35 – Updated: 2026-08-20 15:26
    VLAI
    Title
    Improper Access Control in Experiment History through the REST API in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-08-20 15:13 UTC
    CWE
    • CWE-639 - The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-76397",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-08-20T15:13:03.119856Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-08-20T15:26:32.279Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a user who holds the \"power\" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. For more information see [Experiment Assistants](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a user who holds the \"power\" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 8.1,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-639",
                  "description": "The system\u0027s authorization functionality does not prevent one user from gaining access to another user\u0027s data or record by modifying the key value identifying the data.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:13.301Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Improper Access Control in Experiment History through the REST API in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76397",
        "datePublished": "2026-08-19T21:35:13.301Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-20T15:26:32.279Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76396 (GCVE-0-2026-76396)

    Vulnerability from nvd – Published: 2026-08-19 21:35 – Updated: 2026-08-20 15:26
    VLAI
    Title
    Improper Access Control through Scheduled Searches in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a user that holds a role with the schedule_search capability could cause a scheduled search to load and deserialize a model file through the apply search command. The improper access control is possible because Splunk AI Toolkit does not mark the apply search command as risky. For more information see Troubleshoot the AI Toolkit (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/5.7.3/troubleshooting-the-ai-toolkit/troubleshoot-the-ai-toolkit) in the Splunk documentation.
    SSVC
    Exploitation: none Automatable: no Technical Impact: total
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-08-20 15:13 UTC
    CWE
    • CWE-269 - The software does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-76396",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "total"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-08-20T15:13:29.168674Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-08-20T15:26:32.441Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a user that holds a role with the schedule_search capability could cause a scheduled search to load and deserialize a model file through the apply search command. The improper access control is possible because Splunk AI Toolkit does not mark the apply search command as risky. For more information see [Troubleshoot the AI Toolkit](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/5.7.3/troubleshooting-the-ai-toolkit/troubleshoot-the-ai-toolkit) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a user that holds a role with the schedule_search capability could cause a scheduled search to load and deserialize a model file through the apply search command. The improper access control is possible because Splunk AI Toolkit does not mark the apply search command as risky. For more information see Troubleshoot the AI Toolkit (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/5.7.3/troubleshooting-the-ai-toolkit/troubleshoot-the-ai-toolkit) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 7.5,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-269",
                  "description": "The software does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:12.735Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Improper Access Control through Scheduled Searches in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76396",
        "datePublished": "2026-08-19T21:35:12.735Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-20T15:26:32.441Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76395 (GCVE-0-2026-76395)

    Vulnerability from nvd – Published: 2026-08-19 21:35 – Updated: 2026-08-19 21:35
    VLAI
    Title
    Remote Code Execution (RCE) through Deserialization of Untrusted Data in the Model Loading REST API in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could execute arbitrary code on the Splunk server by loading a model file containing crafted sparse matrix data. The deserialization of untrusted data is possible because a model codec in Splunk AI Toolkit deserializes sparse matrix data without guarding against embedded pickle content. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation.
    CWE
    • CWE-502 - The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a user who holds the \"power\" Splunk role could execute arbitrary code on the Splunk server by loading a model file containing crafted sparse matrix data. The deserialization of untrusted data is possible because a model codec in Splunk AI Toolkit deserializes sparse matrix data without guarding against embedded pickle content. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a user who holds the \"power\" Splunk role could execute arbitrary code on the Splunk server by loading a model file containing crafted sparse matrix data. The deserialization of untrusted data is possible because a model codec in Splunk AI Toolkit deserializes sparse matrix data without guarding against embedded pickle content. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 8.8,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-502",
                  "description": "The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:12.154Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Remote Code Execution (RCE) through Deserialization of Untrusted Data in the Model Loading REST API in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76395",
        "datePublished": "2026-08-19T21:35:12.154Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-19T21:35:12.154Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76394 (GCVE-0-2026-76394)

    Vulnerability from nvd – Published: 2026-08-19 21:35 – Updated: 2026-08-19 21:35
    VLAI
    Title
    Missing Authorization in Container and Connection Management through the REST API in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a low-privileged user who does not hold the "admin" or "power" Splunk roles could start, stop, and configure containers, and read or modify connection and configuration data through the Representational State Transfer (REST) API. The missing authorization is possible because multiple REST API handlers in Splunk AI Toolkit do not enforce authorization checks. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation.
    CWE
    • CWE-862 - The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a low-privileged user who does not hold the \"admin\" or \"power\" Splunk roles could start, stop, and configure containers, and read or modify connection and configuration data through the Representational State Transfer (REST) API. The missing authorization is possible because multiple REST API handlers in Splunk AI Toolkit do not enforce authorization checks. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a low-privileged user who does not hold the \"admin\" or \"power\" Splunk roles could start, stop, and configure containers, and read or modify connection and configuration data through the Representational State Transfer (REST) API. The missing authorization is possible because multiple REST API handlers in Splunk AI Toolkit do not enforce authorization checks. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 8.3,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-862",
                  "description": "The software does not perform an authorization check when an actor attempts to access a resource or perform an action.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:11.547Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Missing Authorization in Container and Connection Management through the REST API in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76394",
        "datePublished": "2026-08-19T21:35:11.547Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-19T21:35:11.547Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76393 (GCVE-0-2026-76393)

    Vulnerability from nvd – Published: 2026-08-19 21:35 – Updated: 2026-08-19 21:35
    VLAI
    Title
    Race Condition during Model Upload through the REST API in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a user who can upload models could overwrite a model being uploaded by another user by sending a concurrent upload request for the same model name, causing the resulting model lookup entry to reference attacker-controlled content. The race condition is possible because Splunk AI Toolkit does not verify that the uploaded content belongs to the request that creates the model lookup entry. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation.
    CWE
    • CWE-362 - The program contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "Shimamine Taihei (\u5cf6\u5cf0 \u6cf0\u5e73)"
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a user who can upload models could overwrite a model being uploaded by another user by sending a concurrent upload request for the same model name, causing the resulting model lookup entry to reference attacker-controlled content. The race condition is possible because Splunk AI Toolkit does not verify that the uploaded content belongs to the request that creates the model lookup entry. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a user who can upload models could overwrite a model being uploaded by another user by sending a concurrent upload request for the same model name, causing the resulting model lookup entry to reference attacker-controlled content. The race condition is possible because Splunk AI Toolkit does not verify that the uploaded content belongs to the request that creates the model lookup entry. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 5.9,
                "baseSeverity": "MEDIUM",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:L",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-362",
                  "description": "The program contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:10.959Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Race Condition during Model Upload through the REST API in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76393",
        "datePublished": "2026-08-19T21:35:10.959Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-19T21:35:10.959Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76392 (GCVE-0-2026-76392)

    Vulnerability from nvd – Published: 2026-08-19 21:35 – Updated: 2026-08-19 21:35
    VLAI
    Title
    Use of Hard-coded Credentials in Container Connections in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the "admin" or "power" Splunk roles could obtain predictable or default credentials for connected container services. The use of hard-coded credentials is possible because Splunk AI Toolkit generates or stores credentials for connected container services using predictable or hard-coded default values. For more information see Connections tab in the AI Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.7.2/ai-toolkit-commands-macros-and-visualizations/connections-tab-in-the-ai-toolkit) in the Splunk documentation.
    CWE
    • CWE-798 - The software contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the \"admin\" or \"power\" Splunk roles could obtain predictable or default credentials for connected container services. The use of hard-coded credentials is possible because Splunk AI Toolkit generates or stores credentials for connected container services using predictable or hard-coded default values. For more information see [Connections tab in the AI Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.7.2/ai-toolkit-commands-macros-and-visualizations/connections-tab-in-the-ai-toolkit) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the \"admin\" or \"power\" Splunk roles could obtain predictable or default credentials for connected container services. The use of hard-coded credentials is possible because Splunk AI Toolkit generates or stores credentials for connected container services using predictable or hard-coded default values. For more information see Connections tab in the AI Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.7.2/ai-toolkit-commands-macros-and-visualizations/connections-tab-in-the-ai-toolkit) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 5.4,
                "baseSeverity": "MEDIUM",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-798",
                  "description": "The software contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:10.371Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Use of Hard-coded Credentials in Container Connections in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76392",
        "datePublished": "2026-08-19T21:35:10.371Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-19T21:35:10.371Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76391 (GCVE-0-2026-76391)

    Vulnerability from nvd – Published: 2026-08-19 21:35 – Updated: 2026-08-19 21:35
    VLAI
    Title
    Improper Privilege Management through Agent Run History in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the "admin" or "power" Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see AI Toolkit Agent Launchpad (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation.
    CWE
    • CWE-863 - The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the \"admin\" or \"power\" Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see [AI Toolkit Agent Launchpad](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the \"admin\" or \"power\" Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see AI Toolkit Agent Launchpad (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 8.3,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-863",
                  "description": "The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:09.768Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Improper Privilege Management through Agent Run History in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76391",
        "datePublished": "2026-08-19T21:35:09.768Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-19T21:35:09.768Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-20266 (GCVE-0-2026-20266)

    Vulnerability from nvd – Published: 2026-06-17 17:07 – Updated: 2026-06-17 18:04
    VLAI
    Title
    OS Command Injection in the btool Configuration Helper in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 5.7.4, a user who holds the "admin" Splunk role could execute arbitrary OS commands on the host running the Splunk Enterprise instance. The vulnerability is possible because of an unsafe shell execution pattern in the btool configuration helper, which constructs OS command strings from dynamic parameters without disabling shell interpretation.
    SSVC
    Exploitation: none Automatable: no Technical Impact: total
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-06-17 18:03 UTC
    CWE
    • CWE-78 - The software constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
    • CWE-78 - Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 5.7.4 (custom)
    Create a notification for this product.
    Date Public
    2026-06-17 00:00
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-20266",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "total"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-06-17T18:03:52.980872Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "problemTypes": [
              {
                "descriptions": [
                  {
                    "cweId": "CWE-78",
                    "description": "CWE-78 Improper Neutralization of Special Elements used in an OS Command (\u0027OS Command Injection\u0027)",
                    "lang": "en",
                    "type": "CWE"
                  }
                ]
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-06-17T18:04:08.968Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "5.7.4",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-06-17T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "In Splunk AI Toolkit versions below 5.7.4, a user who holds the \"admin\" Splunk role could execute arbitrary OS commands on the host running the Splunk Enterprise instance.  \n\nThe vulnerability is possible because of an unsafe shell execution pattern in the btool configuration helper, which constructs OS command strings from dynamic parameters without disabling shell interpretation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 5.7.4, a user who holds the \"admin\" Splunk role could execute arbitrary OS commands on the host running the Splunk Enterprise instance.  \n\nThe vulnerability is possible because of an unsafe shell execution pattern in the btool configuration helper, which constructs OS command strings from dynamic parameters without disabling shell interpretation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 9.1,
                "baseSeverity": "CRITICAL",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-78",
                  "description": "The software constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-06-17T17:07:24.598Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0614"
            }
          ],
          "source": {
            "advisory": "SVD-2026-0614"
          },
          "title": "OS Command Injection in the btool Configuration Helper in Splunk AI Toolkit"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-20266",
        "datePublished": "2026-06-17T17:07:24.598Z",
        "dateReserved": "2025-10-08T11:59:15.402Z",
        "dateUpdated": "2026-06-17T18:04:08.968Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-20265 (GCVE-0-2026-20265)

    Vulnerability from nvd – Published: 2026-06-17 17:07 – Updated: 2026-06-17 18:04
    VLAI
    Title
    Insecure Default Domain Allowlist in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 5.7.4, a low-privileged user that does not hold the "admin" or "power" Splunk roles could cause the Splunk AI Toolkit to make outbound requests over HTTP to a server that an attacker controls, which could allow for data exfiltration. The vulnerability exists because of an insecure default domain allowlist in the Splunk AI Toolkit, which does not restrict outbound AI agent requests to approved external domains.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-06-17 18:04 UTC
    CWE
    • CWE-1188 - The software initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 5.7.4 (custom)
    Create a notification for this product.
    Date Public
    2026-06-17 00:00
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-20265",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-06-17T18:04:24.981105Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-06-17T18:04:30.312Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "5.7.4",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-06-17T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "In Splunk AI Toolkit versions below 5.7.4, a low-privileged user that does not hold the \"admin\" or \"power\" Splunk roles could cause the Splunk AI Toolkit to make outbound requests over HTTP to a server that an attacker controls, which could allow for data exfiltration.  \n\nThe vulnerability exists because of an insecure default domain allowlist in the Splunk AI Toolkit, which does not restrict outbound AI agent  requests to approved external domains."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 5.7.4, a low-privileged user that does not hold the \"admin\" or \"power\" Splunk roles could cause the Splunk AI Toolkit to make outbound requests over HTTP to a server that an attacker controls, which could allow for data exfiltration.  \n\nThe vulnerability exists because of an insecure default domain allowlist in the Splunk AI Toolkit, which does not restrict outbound AI agent  requests to approved external domains."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 4.3,
                "baseSeverity": "MEDIUM",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-1188",
                  "description": "The software initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-06-17T17:07:19.943Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0613"
            }
          ],
          "source": {
            "advisory": "SVD-2026-0613"
          },
          "title": "Insecure Default Domain Allowlist in Splunk AI Toolkit"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-20265",
        "datePublished": "2026-06-17T17:07:19.943Z",
        "dateReserved": "2025-10-08T11:59:15.402Z",
        "dateUpdated": "2026-06-17T18:04:30.312Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-20238 (GCVE-0-2026-20238)

    Vulnerability from nvd – Published: 2026-05-20 16:32 – Updated: 2026-05-20 17:48
    VLAI
    Title
    Improper Access Control through Role Inheritance in Splunk AI Toolkit app
    Summary
    In Splunk AI Toolkit versions below 5.7.3, a low-privileged user that does not hold the 'admin' or 'power' roles could access confidential data that was restricted through `srchFilter` configurations on custom roles.<br><br>The app contains an `authorize.conf` configuration file with a `srchFilter` entry that modifies the built-in ‘user’ role. Because the Splunk platform combines inherited search filters with the `OR` SPL operator, the injected filter overrides more restrictive filters on child roles.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-05-20 17:48 UTC
    CWE
    • CWE-863 - The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 5.7.3 (custom)
    Create a notification for this product.
    Date Public
    2026-05-20 00:00
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-20238",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-05-20T17:48:33.784566Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-05-20T17:48:46.704Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "5.7.3",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "value": "Martin Muller, Splunk"
            }
          ],
          "datePublic": "2026-05-20T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "In Splunk AI Toolkit versions below 5.7.3, a low-privileged user that does not hold the \u0027admin\u0027 or \u0027power\u0027 roles could access confidential data that was restricted through `srchFilter` configurations on custom roles.\u003cbr\u003e\u003cbr\u003eThe app contains an `authorize.conf` configuration file with a `srchFilter` entry that modifies the built-in \u2018user\u2019 role. Because the Splunk platform combines inherited search filters with the `OR` SPL operator, the injected filter overrides more restrictive filters on child roles."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 5.7.3, a low-privileged user that does not hold the \u0027admin\u0027 or \u0027power\u0027 roles could access confidential data that was restricted through `srchFilter` configurations on custom roles.\u003cbr\u003e\u003cbr\u003eThe app contains an `authorize.conf` configuration file with a `srchFilter` entry that modifies the built-in \u2018user\u2019 role. Because the Splunk platform combines inherited search filters with the `OR` SPL operator, the injected filter overrides more restrictive filters on child roles."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 6.5,
                "baseSeverity": "MEDIUM",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-863",
                  "description": "The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-05-20T16:32:19.740Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0502"
            }
          ],
          "source": {
            "advisory": "SVD-2026-0502"
          },
          "title": "Improper Access Control through Role Inheritance in Splunk AI Toolkit app"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-20238",
        "datePublished": "2026-05-20T16:32:19.740Z",
        "dateReserved": "2025-10-08T11:59:15.400Z",
        "dateUpdated": "2026-05-20T17:48:46.704Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76399 (GCVE-0-2026-76399)

    Vulnerability from cvelistv5 – Published: 2026-08-19 21:35 – Updated: 2026-08-19 21:35
    VLAI
    Title
    Incorrect Permission Assignment for Scheduled Searches in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.1, a user who holds the "power" Splunk role could modify app-provided scheduled searches to run arbitrary Search Processing Language (SPL) using the permissions of the search owner, which could allow access to all relevant data and affect system integrity. The vulnerability is possible because Splunk AI Toolkit gives the "power" Splunk role permission to modify scheduled searches that run using the permissions of the search owner.
    CWE
    • CWE-732 - The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 6.0 , < 6.0.1 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.1",
                  "status": "affected",
                  "version": "6.0",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.1, a user who holds the \"power\" Splunk role could modify app-provided scheduled searches to run arbitrary Search Processing Language (SPL) using the permissions of the search owner, which could allow access to all relevant data and affect system integrity. The vulnerability is possible because Splunk AI Toolkit gives the \"power\" Splunk role permission to modify scheduled searches that run using the permissions of the search owner."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.1, a user who holds the \"power\" Splunk role could modify app-provided scheduled searches to run arbitrary Search Processing Language (SPL) using the permissions of the search owner, which could allow access to all relevant data and affect system integrity. The vulnerability is possible because Splunk AI Toolkit gives the \"power\" Splunk role permission to modify scheduled searches that run using the permissions of the search owner."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 8.1,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-732",
                  "description": "The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:14.514Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Incorrect Permission Assignment for Scheduled Searches in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76399",
        "datePublished": "2026-08-19T21:35:14.514Z",
        "dateReserved": "2026-08-19T12:02:03.632Z",
        "dateUpdated": "2026-08-19T21:35:14.514Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76398 (GCVE-0-2026-76398)

    Vulnerability from cvelistv5 – Published: 2026-08-19 21:35 – Updated: 2026-08-20 15:26
    VLAI
    Title
    Improper Access Control during Experiment History Deletion through the REST API in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.1, a user who does not hold the "admin" or "power" Splunk roles could delete the experiment history of another user without permission through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk AI Toolkit deletes experiment history before it verifies that the user can delete the associated experiment. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-08-20 15:12 UTC
    CWE
    • CWE-862 - The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 6.0 , < 6.0.1 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-76398",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-08-20T15:12:25.499797Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-08-20T15:26:32.108Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.1",
                  "status": "affected",
                  "version": "6.0",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.1, a user who does not hold the \"admin\" or \"power\" Splunk roles could delete the experiment history of another user without permission through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk AI Toolkit deletes experiment history before it verifies that the user can delete the associated experiment. For more information see [Experiment Assistants](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.1, a user who does not hold the \"admin\" or \"power\" Splunk roles could delete the experiment history of another user without permission through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk AI Toolkit deletes experiment history before it verifies that the user can delete the associated experiment. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 4.3,
                "baseSeverity": "MEDIUM",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-862",
                  "description": "The software does not perform an authorization check when an actor attempts to access a resource or perform an action.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:13.913Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Improper Access Control during Experiment History Deletion through the REST API in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76398",
        "datePublished": "2026-08-19T21:35:13.913Z",
        "dateReserved": "2026-08-19T12:02:03.632Z",
        "dateUpdated": "2026-08-20T15:26:32.108Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76397 (GCVE-0-2026-76397)

    Vulnerability from cvelistv5 – Published: 2026-08-19 21:35 – Updated: 2026-08-20 15:26
    VLAI
    Title
    Improper Access Control in Experiment History through the REST API in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-08-20 15:13 UTC
    CWE
    • CWE-639 - The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-76397",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-08-20T15:13:03.119856Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-08-20T15:26:32.279Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a user who holds the \"power\" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. For more information see [Experiment Assistants](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a user who holds the \"power\" Splunk role could access and delete all relevant data in experiment history, including data associated with other users. The vulnerability is possible because Splunk AI Toolkit does not preserve the trusted experiment scope when it processes caller-controlled query values before accessing restricted history data. For more information see Experiment Assistants (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.6.4/experiment-assistants) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 8.1,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-639",
                  "description": "The system\u0027s authorization functionality does not prevent one user from gaining access to another user\u0027s data or record by modifying the key value identifying the data.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:13.301Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Improper Access Control in Experiment History through the REST API in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76397",
        "datePublished": "2026-08-19T21:35:13.301Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-20T15:26:32.279Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76396 (GCVE-0-2026-76396)

    Vulnerability from cvelistv5 – Published: 2026-08-19 21:35 – Updated: 2026-08-20 15:26
    VLAI
    Title
    Improper Access Control through Scheduled Searches in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a user that holds a role with the schedule_search capability could cause a scheduled search to load and deserialize a model file through the apply search command. The improper access control is possible because Splunk AI Toolkit does not mark the apply search command as risky. For more information see Troubleshoot the AI Toolkit (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/5.7.3/troubleshooting-the-ai-toolkit/troubleshoot-the-ai-toolkit) in the Splunk documentation.
    SSVC
    Exploitation: none Automatable: no Technical Impact: total
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-08-20 15:13 UTC
    CWE
    • CWE-269 - The software does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-76396",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "total"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-08-20T15:13:29.168674Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-08-20T15:26:32.441Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a user that holds a role with the schedule_search capability could cause a scheduled search to load and deserialize a model file through the apply search command. The improper access control is possible because Splunk AI Toolkit does not mark the apply search command as risky. For more information see [Troubleshoot the AI Toolkit](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/5.7.3/troubleshooting-the-ai-toolkit/troubleshoot-the-ai-toolkit) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a user that holds a role with the schedule_search capability could cause a scheduled search to load and deserialize a model file through the apply search command. The improper access control is possible because Splunk AI Toolkit does not mark the apply search command as risky. For more information see Troubleshoot the AI Toolkit (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/5.7.3/troubleshooting-the-ai-toolkit/troubleshoot-the-ai-toolkit) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 7.5,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-269",
                  "description": "The software does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:12.735Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Improper Access Control through Scheduled Searches in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76396",
        "datePublished": "2026-08-19T21:35:12.735Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-20T15:26:32.441Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76395 (GCVE-0-2026-76395)

    Vulnerability from cvelistv5 – Published: 2026-08-19 21:35 – Updated: 2026-08-19 21:35
    VLAI
    Title
    Remote Code Execution (RCE) through Deserialization of Untrusted Data in the Model Loading REST API in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a user who holds the "power" Splunk role could execute arbitrary code on the Splunk server by loading a model file containing crafted sparse matrix data. The deserialization of untrusted data is possible because a model codec in Splunk AI Toolkit deserializes sparse matrix data without guarding against embedded pickle content. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation.
    CWE
    • CWE-502 - The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a user who holds the \"power\" Splunk role could execute arbitrary code on the Splunk server by loading a model file containing crafted sparse matrix data. The deserialization of untrusted data is possible because a model codec in Splunk AI Toolkit deserializes sparse matrix data without guarding against embedded pickle content. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a user who holds the \"power\" Splunk role could execute arbitrary code on the Splunk server by loading a model file containing crafted sparse matrix data. The deserialization of untrusted data is possible because a model codec in Splunk AI Toolkit deserializes sparse matrix data without guarding against embedded pickle content. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 8.8,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-502",
                  "description": "The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:12.154Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Remote Code Execution (RCE) through Deserialization of Untrusted Data in the Model Loading REST API in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76395",
        "datePublished": "2026-08-19T21:35:12.154Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-19T21:35:12.154Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76394 (GCVE-0-2026-76394)

    Vulnerability from cvelistv5 – Published: 2026-08-19 21:35 – Updated: 2026-08-19 21:35
    VLAI
    Title
    Missing Authorization in Container and Connection Management through the REST API in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a low-privileged user who does not hold the "admin" or "power" Splunk roles could start, stop, and configure containers, and read or modify connection and configuration data through the Representational State Transfer (REST) API. The missing authorization is possible because multiple REST API handlers in Splunk AI Toolkit do not enforce authorization checks. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation.
    CWE
    • CWE-862 - The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a low-privileged user who does not hold the \"admin\" or \"power\" Splunk roles could start, stop, and configure containers, and read or modify connection and configuration data through the Representational State Transfer (REST) API. The missing authorization is possible because multiple REST API handlers in Splunk AI Toolkit do not enforce authorization checks. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a low-privileged user who does not hold the \"admin\" or \"power\" Splunk roles could start, stop, and configure containers, and read or modify connection and configuration data through the Representational State Transfer (REST) API. The missing authorization is possible because multiple REST API handlers in Splunk AI Toolkit do not enforce authorization checks. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 8.3,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-862",
                  "description": "The software does not perform an authorization check when an actor attempts to access a resource or perform an action.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:11.547Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Missing Authorization in Container and Connection Management through the REST API in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76394",
        "datePublished": "2026-08-19T21:35:11.547Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-19T21:35:11.547Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76393 (GCVE-0-2026-76393)

    Vulnerability from cvelistv5 – Published: 2026-08-19 21:35 – Updated: 2026-08-19 21:35
    VLAI
    Title
    Race Condition during Model Upload through the REST API in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a user who can upload models could overwrite a model being uploaded by another user by sending a concurrent upload request for the same model name, causing the resulting model lookup entry to reference attacker-controlled content. The race condition is possible because Splunk AI Toolkit does not verify that the uploaded content belongs to the request that creates the model lookup entry. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation.
    CWE
    • CWE-362 - The program contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "Shimamine Taihei (\u5cf6\u5cf0 \u6cf0\u5e73)"
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a user who can upload models could overwrite a model being uploaded by another user by sending a concurrent upload request for the same model name, causing the resulting model lookup entry to reference attacker-controlled content. The race condition is possible because Splunk AI Toolkit does not verify that the uploaded content belongs to the request that creates the model lookup entry. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a user who can upload models could overwrite a model being uploaded by another user by sending a concurrent upload request for the same model name, causing the resulting model lookup entry to reference attacker-controlled content. The race condition is possible because Splunk AI Toolkit does not verify that the uploaded content belongs to the request that creates the model lookup entry. For more information see Troubleshoot the Splunk Machine Learning Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/machine-learning-toolkit-user-guide/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 5.9,
                "baseSeverity": "MEDIUM",
                "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:H/A:L",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-362",
                  "description": "The program contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:10.959Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Race Condition during Model Upload through the REST API in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76393",
        "datePublished": "2026-08-19T21:35:10.959Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-19T21:35:10.959Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76392 (GCVE-0-2026-76392)

    Vulnerability from cvelistv5 – Published: 2026-08-19 21:35 – Updated: 2026-08-19 21:35
    VLAI
    Title
    Use of Hard-coded Credentials in Container Connections in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the "admin" or "power" Splunk roles could obtain predictable or default credentials for connected container services. The use of hard-coded credentials is possible because Splunk AI Toolkit generates or stores credentials for connected container services using predictable or hard-coded default values. For more information see Connections tab in the AI Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.7.2/ai-toolkit-commands-macros-and-visualizations/connections-tab-in-the-ai-toolkit) in the Splunk documentation.
    CWE
    • CWE-798 - The software contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the \"admin\" or \"power\" Splunk roles could obtain predictable or default credentials for connected container services. The use of hard-coded credentials is possible because Splunk AI Toolkit generates or stores credentials for connected container services using predictable or hard-coded default values. For more information see [Connections tab in the AI Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.7.2/ai-toolkit-commands-macros-and-visualizations/connections-tab-in-the-ai-toolkit) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the \"admin\" or \"power\" Splunk roles could obtain predictable or default credentials for connected container services. The use of hard-coded credentials is possible because Splunk AI Toolkit generates or stores credentials for connected container services using predictable or hard-coded default values. For more information see Connections tab in the AI Toolkit (https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.7.2/ai-toolkit-commands-macros-and-visualizations/connections-tab-in-the-ai-toolkit) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 5.4,
                "baseSeverity": "MEDIUM",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-798",
                  "description": "The software contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:10.371Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Use of Hard-coded Credentials in Container Connections in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76392",
        "datePublished": "2026-08-19T21:35:10.371Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-19T21:35:10.371Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-76391 (GCVE-0-2026-76391)

    Vulnerability from cvelistv5 – Published: 2026-08-19 21:35 – Updated: 2026-08-19 21:35
    VLAI
    Title
    Improper Privilege Management through Agent Run History in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the "admin" or "power" Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see AI Toolkit Agent Launchpad (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation.
    CWE
    • CWE-863 - The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 6.0.0 (custom)
    Create a notification for this product.
    Date Public
    2026-08-19 00:00
    Show details on NVD website

    {
      "containers": {
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "6.0.0",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "reporter",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-08-19T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/markdown",
                  "value": "In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the \"admin\" or \"power\" Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see [AI Toolkit Agent Launchpad](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 6.0.0, a user who does not hold the \"admin\" or \"power\" Splunk roles could run searches with system-level privileges, access all relevant data, affect system integrity, and read or delete search jobs belonging to other users through Agent Run History. The improper privilege management is possible because the Agent Run History handler replaces the calling user session key with a system authentication token before it performs search operations. For more information see AI Toolkit Agent Launchpad (https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/use-ai-toolkit/6.0.0/ai-toolkit-connections-containers-and-agents/ai-toolkit-agent-launchpad) in the Splunk documentation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 8.3,
                "baseSeverity": "HIGH",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-863",
                  "description": "The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-19T21:35:09.768Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0808"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "Upgrade each affected Splunk app or add-on to the applicable fixed version listed in Product Status."
            }
          ],
          "source": {
            "advisory": "SVD-2026-0808"
          },
          "title": "Improper Privilege Management through Agent Run History in Splunk AI Toolkit",
          "workarounds": [
            {
              "lang": "en",
              "value": "Turn off or remove the Splunk AI Toolkit app. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation. Note: turning off Splunk AI Toolkit turns off AI Toolkit Search Processing Language (SPL) commands and model operations. Splunk App for Data Science and Deep Learning and custom search commands that depend on AI Toolkit models or APIs might stop functioning. Unrelated Splunk custom search commands are not affected. For more information see [Troubleshoot the Splunk Machine Learning Toolkit](https://help.splunk.com/en/splunk-cloud-platform/apply-machine-learning/use-ai-toolkit/5.5.0/troubleshooting-mltk/troubleshoot-the-splunk-machine-learning-toolkit) and [DSDL install/version dependencies](https://help.splunk.com/en/splunk-enterprise/apply-machine-learning/splunk-app-for-data-science-and-deep-learning/5.1/install-and-configure-the-splunk-app-for-data-science-and-deep-learning/install-or-upgrade-the-splunk-app-for-data-science-and-deep-learning) in the Splunk documentation."
            }
          ]
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-76391",
        "datePublished": "2026-08-19T21:35:09.768Z",
        "dateReserved": "2026-08-19T12:02:03.631Z",
        "dateUpdated": "2026-08-19T21:35:09.768Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-20266 (GCVE-0-2026-20266)

    Vulnerability from cvelistv5 – Published: 2026-06-17 17:07 – Updated: 2026-06-17 18:04
    VLAI
    Title
    OS Command Injection in the btool Configuration Helper in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 5.7.4, a user who holds the "admin" Splunk role could execute arbitrary OS commands on the host running the Splunk Enterprise instance. The vulnerability is possible because of an unsafe shell execution pattern in the btool configuration helper, which constructs OS command strings from dynamic parameters without disabling shell interpretation.
    SSVC
    Exploitation: none Automatable: no Technical Impact: total
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-06-17 18:03 UTC
    CWE
    • CWE-78 - The software constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
    • CWE-78 - Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 5.7.4 (custom)
    Create a notification for this product.
    Date Public
    2026-06-17 00:00
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-20266",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "total"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-06-17T18:03:52.980872Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "problemTypes": [
              {
                "descriptions": [
                  {
                    "cweId": "CWE-78",
                    "description": "CWE-78 Improper Neutralization of Special Elements used in an OS Command (\u0027OS Command Injection\u0027)",
                    "lang": "en",
                    "type": "CWE"
                  }
                ]
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-06-17T18:04:08.968Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "5.7.4",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-06-17T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "In Splunk AI Toolkit versions below 5.7.4, a user who holds the \"admin\" Splunk role could execute arbitrary OS commands on the host running the Splunk Enterprise instance.  \n\nThe vulnerability is possible because of an unsafe shell execution pattern in the btool configuration helper, which constructs OS command strings from dynamic parameters without disabling shell interpretation."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 5.7.4, a user who holds the \"admin\" Splunk role could execute arbitrary OS commands on the host running the Splunk Enterprise instance.  \n\nThe vulnerability is possible because of an unsafe shell execution pattern in the btool configuration helper, which constructs OS command strings from dynamic parameters without disabling shell interpretation."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 9.1,
                "baseSeverity": "CRITICAL",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-78",
                  "description": "The software constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-06-17T17:07:24.598Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0614"
            }
          ],
          "source": {
            "advisory": "SVD-2026-0614"
          },
          "title": "OS Command Injection in the btool Configuration Helper in Splunk AI Toolkit"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-20266",
        "datePublished": "2026-06-17T17:07:24.598Z",
        "dateReserved": "2025-10-08T11:59:15.402Z",
        "dateUpdated": "2026-06-17T18:04:08.968Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-20265 (GCVE-0-2026-20265)

    Vulnerability from cvelistv5 – Published: 2026-06-17 17:07 – Updated: 2026-06-17 18:04
    VLAI
    Title
    Insecure Default Domain Allowlist in Splunk AI Toolkit
    Summary
    In Splunk AI Toolkit versions below 5.7.4, a low-privileged user that does not hold the "admin" or "power" Splunk roles could cause the Splunk AI Toolkit to make outbound requests over HTTP to a server that an attacker controls, which could allow for data exfiltration. The vulnerability exists because of an insecure default domain allowlist in the Splunk AI Toolkit, which does not restrict outbound AI agent requests to approved external domains.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-06-17 18:04 UTC
    CWE
    • CWE-1188 - The software initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 5.7.4 (custom)
    Create a notification for this product.
    Date Public
    2026-06-17 00:00
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-20265",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-06-17T18:04:24.981105Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-06-17T18:04:30.312Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "5.7.4",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "value": "Gabriel Nitu, Splunk"
            }
          ],
          "datePublic": "2026-06-17T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "In Splunk AI Toolkit versions below 5.7.4, a low-privileged user that does not hold the \"admin\" or \"power\" Splunk roles could cause the Splunk AI Toolkit to make outbound requests over HTTP to a server that an attacker controls, which could allow for data exfiltration.  \n\nThe vulnerability exists because of an insecure default domain allowlist in the Splunk AI Toolkit, which does not restrict outbound AI agent  requests to approved external domains."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 5.7.4, a low-privileged user that does not hold the \"admin\" or \"power\" Splunk roles could cause the Splunk AI Toolkit to make outbound requests over HTTP to a server that an attacker controls, which could allow for data exfiltration.  \n\nThe vulnerability exists because of an insecure default domain allowlist in the Splunk AI Toolkit, which does not restrict outbound AI agent  requests to approved external domains."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 4.3,
                "baseSeverity": "MEDIUM",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-1188",
                  "description": "The software initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-06-17T17:07:19.943Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0613"
            }
          ],
          "source": {
            "advisory": "SVD-2026-0613"
          },
          "title": "Insecure Default Domain Allowlist in Splunk AI Toolkit"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-20265",
        "datePublished": "2026-06-17T17:07:19.943Z",
        "dateReserved": "2025-10-08T11:59:15.402Z",
        "dateUpdated": "2026-06-17T18:04:30.312Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }

    CVE-2026-20238 (GCVE-0-2026-20238)

    Vulnerability from cvelistv5 – Published: 2026-05-20 16:32 – Updated: 2026-05-20 17:48
    VLAI
    Title
    Improper Access Control through Role Inheritance in Splunk AI Toolkit app
    Summary
    In Splunk AI Toolkit versions below 5.7.3, a low-privileged user that does not hold the 'admin' or 'power' roles could access confidential data that was restricted through `srchFilter` configurations on custom roles.<br><br>The app contains an `authorize.conf` configuration file with a `srchFilter` entry that modifies the built-in ‘user’ role. Because the Splunk platform combines inherited search filters with the `OR` SPL operator, the injected filter overrides more restrictive filters on child roles.
    SSVC
    Exploitation: none Automatable: no Technical Impact: partial
    CISA Coordinator · CISA-ADP (v2.0.3)
    Decision recorded 2026-05-20 17:48 UTC
    CWE
    • CWE-863 - The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.
    Impacted products
    Vendor Product Version
    Splunk Splunk AI Toolkit Affected: 5.7 , < 5.7.3 (custom)
    Create a notification for this product.
    Date Public
    2026-05-20 00:00
    Show details on NVD website

    {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-20238",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-05-20T17:48:33.784566Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-05-20T17:48:46.704Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "Splunk AI Toolkit",
              "vendor": "Splunk",
              "versions": [
                {
                  "lessThan": "5.7.3",
                  "status": "affected",
                  "version": "5.7",
                  "versionType": "custom"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "value": "Martin Muller, Splunk"
            }
          ],
          "datePublic": "2026-05-20T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "In Splunk AI Toolkit versions below 5.7.3, a low-privileged user that does not hold the \u0027admin\u0027 or \u0027power\u0027 roles could access confidential data that was restricted through `srchFilter` configurations on custom roles.\u003cbr\u003e\u003cbr\u003eThe app contains an `authorize.conf` configuration file with a `srchFilter` entry that modifies the built-in \u2018user\u2019 role. Because the Splunk platform combines inherited search filters with the `OR` SPL operator, the injected filter overrides more restrictive filters on child roles."
                }
              ],
              "value": "In Splunk AI Toolkit versions below 5.7.3, a low-privileged user that does not hold the \u0027admin\u0027 or \u0027power\u0027 roles could access confidential data that was restricted through `srchFilter` configurations on custom roles.\u003cbr\u003e\u003cbr\u003eThe app contains an `authorize.conf` configuration file with a `srchFilter` entry that modifies the built-in \u2018user\u2019 role. Because the Splunk platform combines inherited search filters with the `OR` SPL operator, the injected filter overrides more restrictive filters on child roles."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "baseScore": 6.5,
                "baseSeverity": "MEDIUM",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
                "version": "3.1"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-863",
                  "description": "The software performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.",
                  "lang": "en",
                  "type": "cwe"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-05-20T16:32:19.740Z",
            "orgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
            "shortName": "cisco"
          },
          "references": [
            {
              "url": "https://advisory.splunk.com/advisories/SVD-2026-0502"
            }
          ],
          "source": {
            "advisory": "SVD-2026-0502"
          },
          "title": "Improper Access Control through Role Inheritance in Splunk AI Toolkit app"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "d1c1063e-7a18-46af-9102-31f8928bc633",
        "assignerShortName": "cisco",
        "cveId": "CVE-2026-20238",
        "datePublished": "2026-05-20T16:32:19.740Z",
        "dateReserved": "2025-10-08T11:59:15.400Z",
        "dateUpdated": "2026-05-20T17:48:46.704Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }