{"answers":{"affected":"4 open source packages ship an affected version, including uptime-kuma.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26042 exists.","fix":"Upgrade uptime-kuma to 2.0.0-beta.2 or later.","what":"CVE-2025-26042 is a medium-severity denial of service vulnerability in n/a, published on 17 Mar 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-26042 and fix it if it is affected.\n\nWhat it is: CVE-2025-26042 is a medium-severity denial of service vulnerability in n/a, published on 17 Mar 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26042 exists.\n\nAffected packages and fixed versions:\n- uptime-kuma (npm): affected from 1.15.0 up to 1.23.16; no fix listed\n- uptime-kuma (npm): affected from 1.15.0 up to 1.23.16; no fix listed\n- uptime-kuma (npm): affected from 2.0.0-beta.0; fixed in 2.0.0-beta.2\n- uptime-kuma (npm): affected from 2.0.0-beta.0; fixed in 2.0.0-beta.2\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-26042/ (Markdown: https://insights.sbomify.com/CVE-2025-26042/index.md)","id":"CVE-2025-26042","markdown":"https://insights.sbomify.com/CVE-2025-26042/index.md","name":"CVE-2025-26042","record":{"aliases":["GHSA-hx7h-9vf7-5xhg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Uptime Kuma monitoring","requires_auth":"high_privilege","summary":"An attacker can cause a denial of service in Uptime Kuma by triggering catastrophic backtracking in a regular expression during notification creation.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1333","name":"Inefficient Regular Expression Complexity"}],"description":"Uptime Kuma \u003e== 1.23.0 has a ReDoS vulnerability, specifically when an administrator creates a notification through the web service. If a string is provided it triggers catastrophic backtracking in the regular expression, leading to a ReDoS attack.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Uptime Kuma's Regular Expression in pushdeeer and whapi file Leads to ReDoS Vulnerability Due to Catastrophic Backtracking","id":"CVE-2025-26042","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":4,"n_references":3,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-26047"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["1.15.0"],"last_affected":["1.23.16"],"package":"uptime-kuma","purl":null,"source":"GHSA-hx7h-9vf7-5xhg"},{"ecosystem":"npm","fixed":[],"introduced":["1.15.0"],"last_affected":["1.23.16"],"package":"uptime-kuma","purl":"pkg:npm/uptime-kuma","source":"GHSA-hx7h-9vf7-5xhg"},{"ecosystem":"npm","fixed":["2.0.0-beta.2"],"introduced":["2.0.0-beta.0"],"last_affected":[],"package":"uptime-kuma","purl":null,"source":"GHSA-hx7h-9vf7-5xhg"},{"ecosystem":"npm","fixed":["2.0.0-beta.2"],"introduced":["2.0.0-beta.0"],"last_affected":[],"package":"uptime-kuma","purl":"pkg:npm/uptime-kuma","source":"GHSA-hx7h-9vf7-5xhg"}],"prev":{"headline":"Code injection in n/a","id":"CVE-2025-26014"},"products":["n/a"],"published":"2025-03-17","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-26","vendors":["n/a"]},"summary":"An attacker can cause a denial of service in Uptime Kuma by triggering catastrophic backtracking in a regular expression during notification creation.","url":"https://insights.sbomify.com/CVE-2025-26042/"}