{"answers":{"affected":"3 open source packages ship an affected version, including github.com/nezhahq/nezha.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49397 exists.","fix":"Upgrade github.com/nezhahq/nezha to 2.0.14 or later.","what":"CVE-2026-49397 is a medium-severity vulnerability in nezhahq nezha, published on 12 Jun 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-49397 and fix it if it is affected.\n\nWhat it is: CVE-2026-49397 is a medium-severity vulnerability in nezhahq nezha, published on 12 Jun 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-49397 exists.\n\nAffected packages and fixed versions:\n- github.com/nezhahq/nezha (Go): affected all versions; no fix listed\n- github.com/nezhahq/nezha (Go): affected from 2.0.0; fixed in 2.0.14\n- github.com/nezhahq/nezha (Go): affected from 2.0.0; fixed in 2.0.14\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-49397/ (Markdown: https://insights.sbomify.com/CVE-2026-49397/index.md)","id":"CVE-2026-49397","markdown":"https://insights.sbomify.com/CVE-2026-49397/index.md","name":"CVE-2026-49397","record":{"aliases":["GHSA-vrmh-5mmx-hjwx","GO-2026-5672"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Nezha Monitoring","requires_auth":"none","summary":"Attackers can enumerate private monitoring services and leak their names and timing data via per-server endpoints in Nezha Monitoring.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"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-863","name":"Incorrect Authorization"},{"id":"CWE-285","name":"Improper Authorization"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O\u0026M tool. From version 2.0.0 to before version 2.0.14, private services (`EnableShowInService: false`) are enumerable via per-server endpoints, leaking name and timing data. This issue has been patched in version 2.0.14.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Nezha's private services (`EnableShowInService: false`) are enumerable via per-server endpoints, leaking name and timing data","id":"CVE-2026-49397","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"October CMS: PHP Object Injection via Backend Widget Session Storage","id":"CVE-2026-49400"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/nezhahq/nezha","purl":"pkg:golang/github.com/nezhahq/nezha","source":"GO-2026-5672"},{"ecosystem":"Go","fixed":["2.0.14"],"introduced":["2.0.0"],"last_affected":[],"package":"github.com/nezhahq/nezha","purl":null,"source":"GHSA-vrmh-5mmx-hjwx"},{"ecosystem":"Go","fixed":["2.0.14"],"introduced":["2.0.0"],"last_affected":[],"package":"github.com/nezhahq/nezha","purl":"pkg:golang/github.com/nezhahq/nezha","source":"GHSA-vrmh-5mmx-hjwx"}],"prev":{"headline":"Nezha Monitoring: Cross-site GET request can trigger stored cron commands on a victim's agents","id":"CVE-2026-49396"},"products":["nezha"],"published":"2026-06-12","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-15","vendors":["nezhahq"]},"summary":"Attackers can enumerate private monitoring services and leak their names and timing data via per-server endpoints in Nezha Monitoring.","url":"https://insights.sbomify.com/CVE-2026-49397/"}