How severe is GHSA-8wrg-m8vm-5fvj?

GHSA-8wrg-m8vm-5fvj has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-8wrg-m8vm-5fvj?

GHSA-8wrg-m8vm-5fvj affects the following packages: github.com/kongchuanhujiao/server (Go). Ecosystems affected: Go.

How do I fix GHSA-8wrg-m8vm-5fvj?

Update github.com/kongchuanhujiao/server to 1.3.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8wrg-m8vm-5fvj is resolved across your whole dependency graph.

How do I detect GHSA-8wrg-m8vm-5fvj in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kongchuanhujiao/server. 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-8wrg-m8vm-5fvj 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-8wrg-m8vm-5fvj?

O3 pinpoints whether GHSA-8wrg-m8vm-5fvj 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-8wrg-m8vm-5fvj actively exploited in the wild?

No public exploit code has been indexed for GHSA-8wrg-m8vm-5fvj 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-8wrg-m8vm-5fvj?

GHSA-8wrg-m8vm-5fvj has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 68th 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-8wrg-m8vm-5fvj?

GHSA-8wrg-m8vm-5fvj is classified as CWE-305 (CWE-305), Improper Authentication (CWE-287). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8wrg-m8vm-5fvj published, and has it been updated?

GHSA-8wrg-m8vm-5fvj was published on February 15, 2022 and was last updated on March 13, 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-8wrg-m8vm-5fvj

HIGH

Authentication Bypass by Primary Weakness in github.com/kongchuanhujiao/server

Also known asCVE-2021-21403

Published

Feb 15, 2022

Updated

Mar 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk68th percentile+1.01%

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/kongchuanhujiao/server

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

Impact

Authentication Bypass by Primary Weakness (CWE-305)

Commit:

https://github.com/kongchuanhujiao/server/commit/9a125624f219e496bdf4b07b404816d5a309bdc1

ALL Users is impacted.

Patches

Yes, PLEASE UPGRADE TO v1.3.21-beta.d0ffc0a6

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/kongchuanhujiao/server`	all versions	1.3.21

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/kongchuanhujiao/server. 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/kongchuanhujiao/server to 1.3.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8wrg-m8vm-5fvj 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-8wrg-m8vm-5fvj 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-8wrg-m8vm-5fvj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Authentication Bypass by Primary Weakness (CWE-305) Commit: https://github.com/kongchuanhujiao/server/commit/9a125624f219e496bdf4b07b404816d5a309bdc1 ALL Users is impacted. ### Patches Yes, PLEASE UPGRADE TO v1.3.21-beta.d0ffc0a6

O3 Security · Impact-Aware SCA

Is GHSA-8wrg-m8vm-5fvj in your dependencies?

O3 detects GHSA-8wrg-m8vm-5fvj 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