PatchTheCVEstatping-ng vulnerabilities and fixes
Recent CVEs affecting statping-ng, with upgrade or downgrade steps. 4 tracked.
Also searched as: statping ng.
statping-ng has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2026-02-11. Highest priority: CVE-2024-26480 (score 49/100).
- CVE-2024-26480 HIGH 7.5 DOWNGRADE An issue in Statping-ng v.0.91.0 allows an attacker to obtain sensitive information via a crafted request to t
- CVE-2024-26479 MEDIUM 5.3 DOWNGRADE An issue in Statping-ng v.0.91.0 allows an attacker to obtain sensitive information via a crafted request to t
- CVE-2024-26478 MEDIUM 5.3 DOWNGRADE An issue in Statping-ng v.0.91.0 allows an attacker to obtain sensitive information via a crafted request to t
- CVE-2024-26477 HIGH 7.5 DOWNGRADE An issue in Statping-ng v.0.91.0 allows an attacker to obtain sensitive information via a crafted request to t
FAQ
How do I fix statping-ng vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is statping-ng being exploited right now?
None of the tracked statping-ng CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which statping-ng CVE should I patch first?
CVE-2024-26480 currently ranks highest (49/100): An issue in Statping-ng v.0.91.0 allows an attacker to obtain sensitive information via a crafted request to t.