# CVE-2026-50884: statping-ng allows attackers to escalate privileges to Administrator and access sensitive components

> Attackers can escalate privileges to Administrator and access sensitive components due to incorrect access control in statping-ng.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-5442-mh7f-72px, GO-2026-6299

## What is CVE-2026-50884?

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.

### Official description

Incorrect access control in statping-ng v0.93.0 allows attackers to escalate privileges to Administrator and access sensitive components.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-50884?

3 open source packages ship an affected version, including github.com/statping-ng/statping-ng.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/statping-ng/statping-ng` | Go | All versions | None |
| `github.com/statping-ng/statping-ng` | Go | All versions to 0.93.0 | None |
| `github.com/statping-ng/statping-ng` | Go | All versions to 0.93.0 | None |

## How do I fix CVE-2026-50884?

Upgrade to a fixed version.

## Is CVE-2026-50884 being exploited?

There is no known exploitation of CVE-2026-50884 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50884 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-50884 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/statping-ng/statping-ng (Go): affected all versions; no fix listed
- github.com/statping-ng/statping-ng (Go): affected all versions up to 0.93.0; no fix listed
- github.com/statping-ng/statping-ng (Go): affected all versions up to 0.93.0; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50884/ (Markdown: https://insights.sbomify.com/CVE-2026-50884/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50884
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50884
- OSV: https://osv.dev/vulnerability/CVE-2026-50884

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50884/
Summaries are generated and may contain mistakes; the official description above is the record.