NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
CRITICAL severity

Path Traversal in BeegoGHSA-95f9-94vc-665h

CRITICALFix: beego/beego#5025

GHSA-95f9-94vc-665h is a critical-severity (CVSS 9.8) Path Traversal vulnerability in github.com/beego/beego. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/beego/beego — see the affected versions and patch details below.

Also known asCVE-2022-31836GO-2022-0569
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk
0.00%0.72%1.44%2.16%0.5%1.7%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐹github.com/beego/beego🐹github.com/beego/beego/v2

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

The leafInfo.match() function in Beego v2.0.3 and below uses path.join() to deal with wildcardvalues which can lead to cross directory risk.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/beego/beegoall versions1.12.11go get github.com/beego/beego@v1.12.11
🐹Gogithub.com/beego/beego/v2≥ 2.0.0&&< 2.0.42.0.4go get github.com/beego/beego/v2@v2.0.4

Affected Products

1 product · 1 configurations
Application
beegobeego
≤ 2.0.3
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

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/beego/beego, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/beego/beego to 1.12.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-95f9-94vc-665h is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

The `leafInfo.match()` function in Beego v2.0.3 and below uses `path.join()` to deal with wildcardvalues which can lead to cross directory risk.
O3 Security · Impact-Aware SCA

Is GHSA-95f9-94vc-665h in your dependencies?

Find it across Go, including transitive dependencies.

Path Traversal in Beego (Critical 9.8)