Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Authentication Bypass by Primary Weakness in github.com/kongchuanhujiao/serverGHSA-8wrg-m8vm-5fvj

HIGHFix: kongchuanhujiao/server@9a12562

GHSA-8wrg-m8vm-5fvj is a high-severity (CVSS 7.5) CWE-305 vulnerability in github.com/kongchuanhujiao/server. A fix is available for github.com/kongchuanhujiao/server — see the affected versions and patch details below.

Also known asCVE-2021-21403
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk
0.00%0.62%1.24%1.86%0.4%1.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-8wrg-m8vm-5fvj by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

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
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/kongchuanhujiao/serverall versions1.3.21go get github.com/kongchuanhujiao/server@v1.3.21

Affected Products

1 product · 1 configurations
Application
kongchuanhujiaokongchuanhujiao_project
< 1.3.21
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/kongchuanhujiao/server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Authentication Bypass by Primary Weakness in…