{"answers":{"affected":"2 open source packages ship an affected version, including uptime-kuma. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32230 exists.","fix":"Upgrade uptime-kuma to 2.2.0 or later.","what":"CVE-2026-32230 is a medium-severity missing authorization vulnerability in louislam uptime-kuma, published on 12 Mar 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-32230 and fix it if it is affected.\n\nWhat it is: CVE-2026-32230 is a medium-severity missing authorization vulnerability in louislam uptime-kuma, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32230 exists.\n\nAffected packages and fixed versions:\n- uptime-kuma (npm): affected from 2.0.0; fixed in 2.2.0\n- uptime-kuma (npm): affected from 2.0.0; fixed in 2.2.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-2026-32230/ (Markdown: https://insights.sbomify.com/CVE-2026-32230/index.md)","id":"CVE-2026-32230","markdown":"https://insights.sbomify.com/CVE-2026-32230/index.md","name":"CVE-2026-32230","record":{"aliases":["GHSA-c7hf-c5p5-5g6h"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Uptime Kuma monitoring tool","requires_auth":"none","summary":"Unauthenticated attackers can access private monitor ping data due to missing authorization checks on the ping badge endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"uptime_kuma","vendor":"uptime.kuma"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Uptime Kuma is an open source, self-hosted monitoring tool. From 2.0.0 to 2.1.3 , the GET /api/badge/:id/ping/:duration? endpoint in server/routers/api-router.js does not verify that the requested monitor belongs to a public group. All other badge endpoints check AND public = 1 in their SQL query before returning data. The ping endpoint skips this check entirely, allowing unauthenticated users to extract average ping/response time data for private monitors. This vulnerability is fixed in 2.2.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-32230.yaml","stars":null,"title":"Uptime-Kuma \u003c v1.23.0 - Improper Access Control"}],"tier":"weaponised"},"has_fix":true,"headline":"Uptime Kuma is Missing Authorization Checks on Ping Badge Endpoint, Leaks Ping times of monitors without needing to be on a status page","id":"CVE-2026-32230","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":5,"next":{"headline":"ZeptoClaw: Generic webhook channel trusts caller-supplied identity fields; allowlist is checked against untrusted payload data","id":"CVE-2026-32231"},"packages":[{"ecosystem":"npm","fixed":["2.2.0"],"introduced":["2.0.0"],"last_affected":[],"package":"uptime-kuma","purl":null,"source":"GHSA-c7hf-c5p5-5g6h"},{"ecosystem":"npm","fixed":["2.2.0"],"introduced":["2.0.0"],"last_affected":[],"package":"uptime-kuma","purl":"pkg:npm/uptime-kuma","source":"GHSA-c7hf-c5p5-5g6h"}],"prev":{"headline":"Auth bypass in Hub","id":"CVE-2026-32229"},"products":["uptime-kuma"],"published":"2026-03-12","related":[{"cvss_score":6.7,"headline":"Uptime Kuma has Persistentent User Sessions","id":"CVE-2023-44400","kev_date_added":null,"published":"2023-10-09"},{"cvss_score":6.5,"headline":"Uptime Kuma: SSTI in Notification Templates Allows Arbitrary File Read (Incomplete Fix for GHSA-vffh-c9pq-4crh)","id":"CVE-2026-33130","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":6.3,"headline":"Attribute Injection leading to XSS(Cross-Site-Scripting) in uptime-kuma","id":"CVE-2023-49276","kev_date_added":null,"published":"2023-12-01"}],"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":"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-13","vendors":["louislam"]},"summary":"Unauthenticated attackers can access private monitor ping data due to missing authorization checks on the ping badge endpoint.","url":"https://insights.sbomify.com/CVE-2026-32230/"}