{"answers":{"affected":"3 open source packages ship an affected version, including github.com/grafana/tempo-operator.","exploited":"There is no known exploitation of CVE-2025-2786 in the wild and no public exploit code.","fix":"Upgrade github.com/grafana/tempo-operator to 0.16.0 or later.","what":"CVE-2025-2786 is a medium-severity vulnerability in Red Hat OpenShift distributed tracing 3, published on 2 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-2786 and fix it if it is affected.\n\nWhat it is: CVE-2025-2786 is a medium-severity vulnerability in Red Hat OpenShift distributed tracing 3, published on 2 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-2786 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/grafana/tempo-operator (Go): affected all versions; fixed in 0.16.0\n- github.com/grafana/tempo-operator (Go): affected all versions; fixed in 0.16.0\n- github.com/grafana/tempo-operator (Go): affected all versions; fixed in 0.16.0\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-2025-2786/ (Markdown: https://insights.sbomify.com/CVE-2025-2786/index.md)","id":"CVE-2025-2786","markdown":"https://insights.sbomify.com/CVE-2025-2786/index.md","name":"CVE-2025-2786","record":{"aliases":["GHSA-28gr-56hr-prp6","GO-2026-4996"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenShift Tempo Operator","requires_auth":"low_privilege","summary":"Attackers with namespace access can extract ServiceAccount tokens to reveal other users' permissions via TokenReview and SubjectAccessReview requests.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"A flaw was found in Tempo Operator, where it creates a ServiceAccount, ClusterRole, and ClusterRoleBinding when a user deploys a TempoStack or TempoMonolithic instance. This flaw allows a user with full access to their namespace to extract the ServiceAccount token and use it to submit TokenReview and SubjectAccessReview requests, potentially revealing information about other users' permissions. While this does not allow privilege escalation or impersonation, it exposes information that could aid in gathering information for further attacks.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Tempo-operator: serviceaccount token exposure leading to token and subject access reviews in openshift tempo operator","id":"CVE-2025-2786","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":3,"n_references":5,"next":{"headline":"Ingress-nginx vulnerability in KNIME Business Hub","id":"CVE-2025-2787"},"packages":[{"ecosystem":"Go","fixed":["0.16.0"],"introduced":["0"],"last_affected":[],"package":"github.com/grafana/tempo-operator","purl":null,"source":"GHSA-28gr-56hr-prp6"},{"ecosystem":"Go","fixed":["0.16.0"],"introduced":["0"],"last_affected":[],"package":"github.com/grafana/tempo-operator","purl":"pkg:golang/github.com/grafana/tempo-operator","source":"GHSA-28gr-56hr-prp6"},{"ecosystem":"Go","fixed":["0.16.0"],"introduced":["0"],"last_affected":[],"package":"github.com/grafana/tempo-operator","purl":"pkg:golang/github.com/grafana/tempo-operator","source":"GO-2026-4996"}],"prev":{"headline":"Libsoup: heap buffer over-read in `skip_insignificant_space` when sniffing content","id":"CVE-2025-2784"},"products":["Red Hat OpenShift distributed tracing 3","Red Hat OpenShift distributed tracing 3.5.3"],"published":"2025-04-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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-09-08","vendors":["Red Hat"]},"summary":"Attackers with namespace access can extract ServiceAccount tokens to reveal other users' permissions via TokenReview and SubjectAccessReview requests.","url":"https://insights.sbomify.com/CVE-2025-2786/"}