{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-76347 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76347 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76347 is a medium-severity server-side request forgery vulnerability in Splunk Splunk, 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-76347 and fix it if it is affected.\n\nWhat it is: CVE-2026-76347 is a medium-severity server-side request forgery vulnerability in Splunk Splunk, 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-76347 in the wild and no public exploit code.\n\nAffected product: Splunk Splunk. 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-76347/ (Markdown: https://insights.sbomify.com/CVE-2026-76347/index.md)","id":"CVE-2026-76347","markdown":"https://insights.sbomify.com/CVE-2026-76347/index.md","name":"CVE-2026-76347","record":{"aliases":["GHSA-q6q4-g44p-g55f"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Secure Gateway","requires_auth":"low_privilege","summary":"An attacker can exploit SSRF in Splunk Secure Gateway to send authenticated requests to internal services, potentially modifying cluster state or causing denial of service.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"splunk","vendor":"splunk"},{"product":"splunk_secure_gateway","vendor":"splunk"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below 3.10.9, 3.9.23, and 3.8.70, a user who does not hold the \"admin\" or \"power\" Splunk roles could use Server-Side Request Forgery (SSRF) in report notifications to send system-authenticated requests to internal Splunk services, which could allow for changes to Search Head Cluster state and a denial of service. The vulnerability is possible because Splunk Secure Gateway does not validate report notification path values before it sends internal requests.","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":"Server-Side Request Forgery (SSRF) through the Report Notifications REST API in Splunk Secure Gateway","id":"CVE-2026-76347","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk"],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Missing Authorization in Search Head Cluster Member Controls in Splunk Enterprise","id":"CVE-2026-76348"},"packages":[],"prev":{"headline":"Stored Cross-Site Scripting (XSS) through Splunk Web Dashboard Sparkline Format Options in Splunk Enterprise","id":"CVE-2026-76346"},"products":["Splunk Enterprise","Splunk Secure Gateway"],"published":"2026-08-19","related":[{"cvss_score":9.8,"headline":"Splunk Enterprise Missing Authentication for Critical Function","id":"CVE-2026-20253","kev_date_added":"2026-06-18","published":"2026-06-10"},{"cvss_score":9.8,"headline":"Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise","id":"CVE-2026-76268","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":9.8,"headline":"Improper Neutralization in Splunk Enterprise","id":"CVE-2026-76284","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":9.8,"headline":"Improper Adherence to Coding Standards in Splunk Enterprise","id":"CVE-2026-76285","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2017-17067","kev_date_added":null,"published":"2017-11-30"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2016-10126","kev_date_added":null,"published":"2017-01-10"},{"cvss_score":9.4,"headline":"Improper Access Control through Embedded Report REST API Requests in Splunk Enterprise","id":"CVE-2026-76310","kev_date_added":null,"published":"2026-08-19"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-08-20","vendors":["Splunk"]},"summary":"An attacker can exploit SSRF in Splunk Secure Gateway to send authenticated requests to internal services, potentially modifying cluster state or causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-76347/"}