{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-76388 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76388 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76388 is a high-severity vulnerability in Splunk Enterprise Security, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76388 and fix it if it is affected.\n\nWhat it is: CVE-2026-76388 is a high-severity vulnerability in Splunk Enterprise Security, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76388 in the wild and no public exploit code.\n\nAffected product: Splunk Enterprise Security. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-76388/ (Markdown: https://insights.sbomify.com/CVE-2026-76388/index.md)","id":"CVE-2026-76388","markdown":"https://insights.sbomify.com/CVE-2026-76388/index.md","name":"CVE-2026-76388","record":{"aliases":["GHSA-hj4g-r7xm-5vg9"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise Security","requires_auth":"low_privilege","summary":"An analyst can modify UEBA search macros to execute with admin privileges, enabling data access and system integrity compromise.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"enterprise_security","vendor":"splunk"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"In Splunk Enterprise Security versions below 8.6.1, a user who holds the ess_analyst Splunk Enterprise Security role could change User and Entity Behavior Analytics (UEBA) search macros that scheduled searches run with administrator permissions, allowing for access to all relevant data and system integrity through those searches. The vulnerability is possible because the UEBA app metadata grants analyst roles write access to search macros that should be writable only by administrator roles. For more information see Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.4/installation/users-and-roles-for-splunk-enterprise-security) and Roles and knowledge objects in UEBA for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.5/user-and-entity-behavior-analytics/roles-and-knowledge-objects-in-ueba-for-splunk-enterprise-security) in the Splunk documentation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege Escalation through Search Macro Permissions in Splunk Enterprise Security","id":"CVE-2026-76388","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Server-Side Request Forgery (SSRF) through the REST API in Cisco Talos Intelligence for Enterprise Security Cloud","id":"CVE-2026-76389"},"packages":[],"prev":{"headline":"SPL Injection through the REST API in Splunk Enterprise Security","id":"CVE-2026-76387"},"products":["Splunk Enterprise Security"],"published":"2026-08-19","related":[{"cvss_score":8.1,"headline":"SPL Injection through the REST API in Splunk Enterprise Security","id":"CVE-2026-76387","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":6.5,"headline":"Denial of Service in Splunk Enterprise Security of the Investigations manager through Investigation creation","id":"CVE-2024-22165","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":4.3,"headline":"Denial of Service of an Investigation in Splunk Enterprise Security through Investigation attachments","id":"CVE-2024-22164","kev_date_added":null,"published":"2024-01-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["Splunk"]},"summary":"An analyst can modify UEBA search macros to execute with admin privileges, enabling data access and system integrity compromise.","url":"https://insights.sbomify.com/CVE-2026-76388/"}