{"answers":{"affected":"3 open source packages ship an affected version, including github.com/statping-ng/statping-ng.","exploited":"There is no known exploitation of CVE-2026-50884 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-50884 is a high-severity vulnerability in n/a, published on 15 Jun 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-50884 and fix it if it is affected.\n\nWhat it is: CVE-2026-50884 is a high-severity vulnerability in n/a, published on 15 Jun 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-50884 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/statping-ng/statping-ng (Go): affected all versions; no fix listed\n- github.com/statping-ng/statping-ng (Go): affected all versions up to 0.93.0; no fix listed\n- github.com/statping-ng/statping-ng (Go): affected all versions up to 0.93.0; no fix listed\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-50884/ (Markdown: https://insights.sbomify.com/CVE-2026-50884/index.md)","id":"CVE-2026-50884","markdown":"https://insights.sbomify.com/CVE-2026-50884/index.md","name":"CVE-2026-50884","record":{"aliases":["GHSA-5442-mh7f-72px","GO-2026-6299"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Status monitoring tool","requires_auth":"low_privilege","summary":"Attackers can escalate privileges to Administrator and access sensitive components due to incorrect access control in statping-ng.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Incorrect access control in statping-ng v0.93.0 allows attackers to escalate privileges to Administrator and access sensitive components.","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":"statping-ng allows attackers to escalate privileges to Administrator and access sensitive components","id":"CVE-2026-50884","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2026-50885"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/statping-ng/statping-ng","purl":"pkg:golang/github.com/statping-ng/statping-ng","source":"GO-2026-6299"},{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":["0.93.0"],"package":"github.com/statping-ng/statping-ng","purl":null,"source":"GHSA-5442-mh7f-72px"},{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":["0.93.0"],"package":"github.com/statping-ng/statping-ng","purl":"pkg:golang/github.com/statping-ng/statping-ng","source":"GHSA-5442-mh7f-72px"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2026-50883"},"products":["n/a"],"published":"2026-06-15","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":"total"},"state":"PUBLISHED","updated":"2026-06-16","vendors":["n/a"]},"summary":"Attackers can escalate privileges to Administrator and access sensitive components due to incorrect access control in statping-ng.","url":"https://insights.sbomify.com/CVE-2026-50884/"}