{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-100525 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-100525 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100525 is a medium-severity missing authorization vulnerability in openclaw diagnostics-prometheus, published on 26 Sep 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-100525 and fix it if it is affected.\n\nWhat it is: CVE-2026-100525 is a medium-severity missing authorization vulnerability in openclaw diagnostics-prometheus, published on 26 Sep 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-100525 in the wild and no public exploit code.\n\nAffected product: openclaw diagnostics-prometheus. 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-100525/ (Markdown: https://insights.sbomify.com/CVE-2026-100525/index.md)","id":"CVE-2026-100525","markdown":"https://insights.sbomify.com/CVE-2026-100525/index.md","name":"CVE-2026-100525","record":{"aliases":["GHSA-49qj-frf3-688h","GHSA-rx8p-qcpv-c7vr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenClaw diagnostics plugin","requires_auth":"low_privilege","summary":"An authenticated user without read scope can access Prometheus metrics in OpenClaw diagnostics plugin when using trusted-proxy authentication.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The OpenClaw Prometheus diagnostics plugin (@openclaw/diagnostics-prometheus) before version 2026.9.3 does not enforce the operator.read scope on its authenticated metrics endpoint. In deployments using an identity-bearing Gateway authentication mode such as trusted-proxy, a caller whose effective role has no read scope can retrieve the diagnostics document even though ordinary read methods reject the same identity, disclosing operational metrics to an authenticated profile intentionally limited below read access. Shared-secret Gateway callers already hold the documented full operator scope and are not affected. The issue is fixed in 2026.9.3; as a workaround, disable the Prometheus endpoint or ensure every identity that can reach it is intended to hold operator.read.","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":"OpenClaw diagnostics-prometheus before 2026.9.3 Authentication Bypass","id":"CVE-2026-100525","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Vulnerability in discord","id":"CVE-2026-100526"},"packages":[],"prev":{"headline":"Cotonti through 1.0.0 Cross-Site Request Forgery via Extensions Manager","id":"CVE-2026-100524"},"products":["diagnostics-prometheus"],"published":"2026-09-26","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":"total"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["openclaw"]},"summary":"An authenticated user without read scope can access Prometheus metrics in OpenClaw diagnostics plugin when using trusted-proxy authentication.","url":"https://insights.sbomify.com/CVE-2026-100525/"}