{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-76401 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76401 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76401 is a medium-severity denial of service vulnerability in Splunk Connect for Kafka, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76401 and fix it if it is affected.\n\nWhat it is: CVE-2026-76401 is a medium-severity denial of service vulnerability in Splunk Connect for Kafka, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76401 in the wild and no public exploit code.\n\nAffected product: Splunk Connect for Kafka. 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-76401/ (Markdown: https://insights.sbomify.com/CVE-2026-76401/index.md)","id":"CVE-2026-76401","markdown":"https://insights.sbomify.com/CVE-2026-76401/index.md","name":"CVE-2026-76401","record":{"aliases":["GHSA-9w75-cvch-h753"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Kafka Connect plugin","requires_auth":"none","summary":"An unauthenticated attacker can cause denial of service in Splunk Connect for Kafka by submitting a malicious regular expression via the REST API.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"connect_for_kafka","vendor":"splunk"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"}],"description":"In Splunk Connect for Kafka versions below 2.2.7, an unauthenticated user who can reach the Kafka Connect Representational State Transfer (REST) API could configure timestamp extraction with a crafted regular expression and matching event data to block a Kafka Connect worker thread, stopping event delivery for the affected connector. The vulnerability is possible because timestamp extraction evaluates customer-supplied regular expressions without a time limit. For more information see Install Splunk Connect for Kafka (https://help.splunk.com/en/data-management/integrate-data-with-add-ons/splunk-connect-for-kafka/2.2/install/install-splunk-connect-for-kafka) and Data ingestion parameters for Splunk Connect for Kafka (https://help.splunk.com/en/data-management/integrate-data-with-add-ons/splunk-connect-for-kafka/2.2/overview/data-ingestion-parameters-for-splunk-connect-for-kafka) 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":false,"headline":"Regular Expression Denial of Service (DoS) through the REST API in Splunk Connect for Kafka","id":"CVE-2026-76401","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Server-Side Request Forgery (SSRF) through the REST API in Splunk Connect for Kafka","id":"CVE-2026-76402"},"packages":[],"prev":{"headline":"Denial of Service (DoS) through the REST API in Splunk Connect for Kafka","id":"CVE-2026-76400"},"products":["Splunk Connect for Kafka"],"published":"2026-08-19","related":[{"cvss_score":8.2,"headline":"Server-Side Request Forgery (SSRF) through the REST API in Splunk Connect for Kafka","id":"CVE-2026-76402","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":7.4,"headline":"Improper Certificate Validation through HTTP Event Collector Kerberos Authentication in Splunk Connect for Kafka","id":"CVE-2026-76403","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":5.9,"headline":"Denial of Service (DoS) through the REST API in Splunk Connect for Kafka","id":"CVE-2026-76400","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 unauthenticated attacker can cause denial of service in Splunk Connect for Kafka by submitting a malicious regular expression via the REST API.","url":"https://insights.sbomify.com/CVE-2026-76401/"}