How severe is GHSA-m983-7426-5hrj?

GHSA-m983-7426-5hrj has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-m983-7426-5hrj?

GHSA-m983-7426-5hrj affects the following packages: github.com/lin-snow/ech0 (Go). Ecosystems affected: Go.

How do I fix GHSA-m983-7426-5hrj?

Update github.com/lin-snow/ech0 to 1.4.8-0.20260322121226-acbf1fd71011 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m983-7426-5hrj is resolved across your whole dependency graph.

How do I detect GHSA-m983-7426-5hrj in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lin-snow/ech0. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-m983-7426-5hrj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-m983-7426-5hrj?

O3 pinpoints whether GHSA-m983-7426-5hrj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m983-7426-5hrj actively exploited in the wild?

No public exploit code has been indexed for GHSA-m983-7426-5hrj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-m983-7426-5hrj?

GHSA-m983-7426-5hrj has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-m983-7426-5hrj?

GHSA-m983-7426-5hrj is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m983-7426-5hrj published, and has it been updated?

GHSA-m983-7426-5hrj was published on March 24, 2026 and was last updated on March 30, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-m983-7426-5hrj

MEDIUM

Ech0 authenticated user-list exposed data via public `/api/allusers` endpoint

Also known asCVE-2026-33638GO-2026-4838

Published

Mar 24, 2026

Updated

Mar 30, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk38th percentile+0.45%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹github.com/lin-snow/ech0

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

A public access-control flaw allows unauthenticated users to retrieve the full user list from GET /api/allusers. This exposes user profile metadata to anyone who can reach the application and enables remote user enumeration.

Details

The vulnerable route is registered as a public endpoint:

internal/router/user.go:17
- appRouterGroup.PublicRouterGroup.GET("/allusers", h.UserHandler.GetAllUsers())

However, the handler appears to have been intended as an authenticated endpoint:

internal/handler/user/user.go:177-185
- API annotations indicate an authentication requirement via @Security ApiKeyAuth

This creates a mismatch between the documented security model and the actual routing configuration. As a result, requests to GET /api/allusers succeed without authentication and return user records, including profile metadata such as usernames, email addresses, role-related flags, avatar values, and locale information.

A negative control against another endpoint that correctly requires authentication further supports that this exposure is unintended: GET /api/user returns 401 Unauthorized when no token is supplied, while GET /api/allusers remains publicly accessible.

Impact

Type: Access control bypass / unauthenticated data exposure
Who is impacted: Any deployment exposing the API to untrusted networks, and all users whose profile metadata is returned by the endpoint
Security impact: Enables remote user enumeration and disclosure of user profile metadata, which may facilitate account reconnaissance, phishing, and targeted credential attacks
Attack preconditions: None beyond network access to the affected API endpoint

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/lin-snow/ech0`	all versions	1.4.8-0.20260322121226-acbf1fd71011

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lin-snow/ech0. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/lin-snow/ech0 to 1.4.8-0.20260322121226-acbf1fd71011 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m983-7426-5hrj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-m983-7426-5hrj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m983-7426-5hrj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary A public access-control flaw allows unauthenticated users to retrieve the full user list from `GET /api/allusers`. This exposes user profile metadata to anyone who can reach the application and enables remote user enumeration. ### Details The vulnerable route is registered as a public endpoint: - `internal/router/user.go:17` - `appRouterGroup.PublicRouterGroup.GET("/allusers", h.UserHandler.GetAllUsers())` However, the handler appears to have been intended as an authenticated endpoint: - `internal/handler/user/user.go:177-185` - API annotations indicate an authentication re

O3 Security · Impact-Aware SCA

Is GHSA-m983-7426-5hrj in your dependencies?

O3 detects GHSA-m983-7426-5hrj across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works