{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-66781 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-66781 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-66781 is a medium-severity vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2, published on 18 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-66781 and fix it if it is affected.\n\nWhat it is: CVE-2026-66781 is a medium-severity vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2, published on 18 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-66781 in the wild and no public exploit code.\n\nAffected product: Red Hat Advanced Cluster Management for Kubernetes 2. 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-66781/ (Markdown: https://insights.sbomify.com/CVE-2026-66781/index.md)","id":"CVE-2026-66781","markdown":"https://insights.sbomify.com/CVE-2026-66781/index.md","name":"CVE-2026-66781","record":{"aliases":["GHSA-gcch-g8g2-6852"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Kubernetes operator","requires_auth":"none","summary":"An attacker can access unencrypted IPsec keys via a debug endpoint, allowing decryption of inter-cluster network traffic.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-749","name":"Exposed Dangerous Method or Function"}],"description":"A flaw was found in the Submariner operator. The Submariner Custom Resource (CR), used for configuring network connectivity, stores the IPsec pre-shared key (PSK) in an unencrypted format. This key, which is critical for securing communication between Kubernetes clusters, can be accessed by unauthorized parties. Such access enables an attacker to passively decrypt network traffic flowing between any two clusters in the mesh, resulting in sensitive information disclosure.","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":"Submariner-operator: pprof debug endpoint enabled by default on 0.0.0.0:8082 without authentication","id":"CVE-2026-66781","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":10,"next":{"headline":"Submariner-operator: operator clusterrole grants cluster-wide create/update on all configmaps","id":"CVE-2026-66782"},"packages":[],"prev":{"headline":"Submariner-operator: broker serviceaccount secret (token + ca) logged in full at trace verbosity","id":"CVE-2026-66780"},"products":["Red Hat Advanced Cluster Management for Kubernetes 2","Red Hat Advanced Cluster Management for Kubernetes 2.11","Red Hat Advanced Cluster Management for Kubernetes 2.13","Red Hat Advanced Cluster Management for Kubernetes 2.14","Red Hat Advanced Cluster Management for Kubernetes 2.15","Red Hat Advanced Cluster Management for Kubernetes 2.16","Red Hat Advanced Cluster Management for Kubernetes 2.17"],"published":"2026-08-18","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","updated":"2026-10-19","vendors":["Red Hat"]},"summary":"An attacker can access unencrypted IPsec keys via a debug endpoint, allowing decryption of inter-cluster network traffic.","url":"https://insights.sbomify.com/CVE-2026-66781/"}