{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-131240 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-131240 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-131240 is a low-severity denial of service vulnerability in Splunk SOAR, published on 19 Nov 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-131240 and fix it if it is affected.\n\nWhat it is: CVE-2026-131240 is a low-severity denial of service vulnerability in Splunk SOAR, published on 19 Nov 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-131240 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected product: Splunk SOAR. 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-131240/ (Markdown: https://insights.sbomify.com/CVE-2026-131240/index.md)","id":"CVE-2026-131240","markdown":"https://insights.sbomify.com/CVE-2026-131240/index.md","name":"CVE-2026-131240","record":{"aliases":["GHSA-g44j-6684-6c2r"],"analysis":{"component_type":"web_application","exploitable_when_present":false,"fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"security orchestration platform","requires_auth":"low_privilege","requires_specific_call":false,"summary":"Authenticated users can fill Splunk SOAR's Ingestion Status history via the container REST API, degrading monitoring availability.","user_interaction":"required","vuln_class":"denial_of_service","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"cisco","component":null,"cpe":[],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"In Splunk SOAR versions below 8.8.0, an authenticated user could cause Splunk SOAR to store excessive data in the Ingestion Status history through the Representational State Transfer (REST) API. When another user with permission to view system settings retrieves the Ingestion Status history, Splunk SOAR could use additional resources and return a larger response, which could degrade the availability of administrative monitoring.\nThe vulnerability is possible because Splunk SOAR does not limit the amount of request data that it records for failed container creation before it stores the data in the Ingestion Status history.\nFor more information see REST Containers (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/6.4.0/container-endpoints/rest-containers), REST Roles and Permissions (https://help.splunk.com/en/splunk-soar/soar-on-premises/rest-api-reference/6.4.0/role-management-endpoints/rest-roles-and-permissions), and View ingested container statistics using Ingestion Status (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.4.1/manage-your-splunk-soar-on-premises-system-health-and-performance/view-ingested-container-statistics-using-ingestion-status) 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":"Denial of Service (DoS) through the Container REST API in Splunk SOAR","id":"CVE-2026-131240","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"Authorization Bypass Through the REST API in Splunk SOAR","id":"CVE-2026-131241"},"nickname":null,"packages":[],"prev":{"headline":"SPL Injection through the System Update Status Report in Splunk Enterprise Security","id":"CVE-2026-131239"},"products":["Splunk SOAR"],"published":"2026-11-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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","text_fixes":[],"updated":"2026-11-20","vendor_status":[],"vendors":["Splunk"]},"summary":"Authenticated users can fill Splunk SOAR's Ingestion Status history via the container REST API, degrading monitoring availability.","url":"https://insights.sbomify.com/CVE-2026-131240/"}