{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-72648 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-72648 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-72648 is a medium-severity vulnerability in Elastic Eck Operator, published on 13 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-72648 and fix it if it is affected.\n\nWhat it is: CVE-2026-72648 is a medium-severity vulnerability in Elastic Eck Operator, published on 13 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-72648 in the wild and no public exploit code.\n\nAffected product: Elastic Eck Operator. 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-72648/ (Markdown: https://insights.sbomify.com/CVE-2026-72648/index.md)","id":"CVE-2026-72648","markdown":"https://insights.sbomify.com/CVE-2026-72648/index.md","name":"CVE-2026-72648","record":{"aliases":["GHSA-994r-4f38-cvgv"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Elastic Cloud on Kubernetes","requires_auth":"low_privilege","summary":"Attackers with namespace read access can retrieve cleartext Elasticsearch service account tokens from workload specifications, bypassing Kubernetes Secret protections.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"elastic_cloud_on_kubernetes","vendor":"elastic"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-526","name":"Cleartext Storage of Sensitive Information in an Environment Variable"}],"description":"Cleartext Storage of Sensitive Information in an Environment Variable (CWE-526) in Elastic Cloud on Kubernetes (ECK) can lead to information disclosure via Retrieve Embedded Sensitive Data (CAPEC-37). When ECK reconciles a Fleet Server resource that authenticates to Elasticsearch with a service account token, the token is written into the generated workload specification in cleartext rather than being referenced from the Kubernetes Secret that ECK maintains for the other credentials on the same path. Any principal able to read workload specifications in the affected namespace can therefore read a live Elasticsearch credential, even when Kubernetes RBAC does not grant that principal access to Secrets.","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":"Information disclosure in Eck Operator","id":"CVE-2026-72648","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Deserialization of Untrusted Data in Elasticsearch Leading to Remote Code Execution","id":"CVE-2026-72649"},"packages":[],"prev":{"headline":"Uncontrolled Recursion in Elasticsearch Leading to Denial of Service","id":"CVE-2026-72647"},"products":["Eck Operator"],"published":"2026-08-13","related":[{"cvss_score":7.5,"headline":"Cryptographic Issues in ECK","id":"CVE-2020-7010","kev_date_added":null,"published":"2020-06-03"},{"cvss_score":6.5,"headline":"Unintended Proxy or Intermediary in Elastic Cloud on Kubernetes Leading to Cross-Namespace Secret Disclosure","id":"CVE-2026-72640","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":5.4,"headline":"Incorrect Authorization in Elastic Cloud on Kubernetes Leading to Unauthorized Modification of Data","id":"CVE-2026-78609","kev_date_added":null,"published":"2026-09-02"},{"cvss_score":5.3,"headline":"Elastic Cloud on Kubernetes (ECK) secret token configuration issue","id":"CVE-2023-31416","kev_date_added":null,"published":"2023-10-26"},{"cvss_score":3.5,"headline":"Incomplete Cleanup in Elastic Cloud on Kubernetes Leading to Unauthorized Cross-Namespace Credential Retention","id":"CVE-2026-78600","kev_date_added":null,"published":"2026-09-02"}],"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-13","vendors":["Elastic"]},"summary":"Attackers with namespace read access can retrieve cleartext Elasticsearch service account tokens from workload specifications, bypassing Kubernetes Secret protections.","url":"https://insights.sbomify.com/CVE-2026-72648/"}