{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2026-20253 in the wild since at least 18 Jun 2026.","fix":"No fix has been published for CVE-2026-20253 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 21 Jun 2026.","what":"CVE-2026-20253 is a critical missing authorization vulnerability in Splunk Splunk, published on 10 Jun 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-20253 and fix it if it is affected.\n\nWhat it is: CVE-2026-20253 is a critical missing authorization vulnerability in Splunk Splunk, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2026-20253 in the wild since at least 18 Jun 2026.\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-20253/ (Markdown: https://insights.sbomify.com/CVE-2026-20253/index.md)","id":"CVE-2026-20253","markdown":"https://insights.sbomify.com/CVE-2026-20253/index.md","name":"CVE-2026-20253","record":{"aliases":["GHSA-xgm5-jh99-wc4v"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise","requires_auth":"none","summary":"Unauthenticated attackers can create or truncate arbitrary files via an unprotected PostgreSQL sidecar endpoint in Splunk Enterprise.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"splunk","vendor":"splunk"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"In Splunk Enterprise 10.2 versions below 10.2.4 and 10 versions below 10.0.7, an unauthenticated user could create or truncate arbitrary files through a PostgreSQL sidecar service endpoint. The vulnerability exists because the PostgreSQL sidecar service endpoint lacks authentication controls, allowing any network-reachable user to invoke file operations without credentials. Splunk Enterprise versions 9.4 and earlier are not affected. If you cannot immediately upgrade to a fixed version, you can mitigate this vulnerability by disabling the PostgreSQL sidecar service.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-06-12","github_poc":7,"max_poc_stars":13,"metasploit":0,"nuclei":1,"refs":[{"date":"2026-06-12T10:04:32Z","kind":"github_poc","ref":"https://github.com/watchtowrlabs/watchTowr-vs-Splunk-CVE-2026-20253","stars":13,"title":null},{"date":"2026-06-13T18:09:32Z","kind":"github_poc","ref":"https://github.com/0xredash/CVE-2026-20253","stars":5,"title":"CVE-2026-20253"},{"date":"2026-06-14T04:18:18Z","kind":"github_poc","ref":"https://github.com/HORKimhab/CVE-2026-20253","stars":0,"title":"CVE-2026-20253 - Splunk Enterprise"},{"date":"2026-06-26T18:13:31Z","kind":"github_poc","ref":"https://github.com/fevar54/CVE-2026-20253-Splunk-Enterprise-Pre-Auth-RCE-","stars":0,"title":"PoC de CVE-2026-20253: RCE pre-autenticacion en Splunk Enterprise."},{"date":"2026-06-29T07:53:55Z","kind":"github_poc","ref":"https://github.com/pssec-io/CVE-2026-20253","stars":0,"title":"POC for CVE-2026-20253"},{"date":"2026-07-18T10:54:12Z","kind":"github_poc","ref":"https://github.com/Het-Kalariya/CVE-2026-20253","stars":0,"title":null},{"date":"2026-09-10T07:14:29Z","kind":"github_poc","ref":"https://github.com/ivanesk315/CVE-2026-20253","stars":0,"title":null},{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-20253.yaml","stars":null,"title":"Splunk Enterprise \u0026 Cloud Platform - Unrestricted File Upload"}],"tier":"exploited"},"has_fix":null,"headline":"Splunk Enterprise Missing Authentication for Critical Function","id":"CVE-2026-20253","indexable":true,"kev":{"dateAdded":"2026-06-18","dueDate":"2026-06-21","knownRansomwareCampaignUse":"Unknown","product":"Enterprise","requiredAction":"Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.","vendorProject":"Splunk","vulnerabilityName":"Splunk Enterprise Missing Authentication for Critical Function Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk"],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Information Disclosure through External Content Restriction Bypass in Splunk Enterprise","id":"CVE-2026-20254"},"packages":[],"prev":{"headline":"Server-Side Request Forgery (SSRF) through Dashboard Studio PDF Export in Splunk Enterprise","id":"CVE-2026-20252"},"products":["Splunk Enterprise"],"published":"2026-06-10","related":[{"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":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-19","vendors":["Splunk"]},"summary":"Unauthenticated attackers can create or truncate arbitrary files via an unprotected PostgreSQL sidecar endpoint in Splunk Enterprise.","url":"https://insights.sbomify.com/CVE-2026-20253/"}