How severe is CVE-2022-31836?

CVE-2022-31836 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-31836?

CVE-2022-31836 affects the following packages: github.com/beego/beego (Go), github.com/beego/beego/v2 (Go). Ecosystems affected: Go.

How do I fix CVE-2022-31836?

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 CVE-2022-31836 is resolved across your whole dependency graph.

How do I detect CVE-2022-31836 in my Go dependencies?

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.

How do I mitigate CVE-2022-31836 if there is no patch (or I can't update yet)?

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.

Is CVE-2022-31836 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-31836, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-31836?

CVE-2022-31836 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th 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 CVE-2022-31836?

CVE-2022-31836 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-31836 published, and has it been updated?

CVE-2022-31836 was published on July 5, 2022 and was last updated on October 28, 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

Not in CISA KEV

CRITICAL severity

CVE-2022-31836 — beego

CRITICALFix: beego/beego#5025

CVE-2022-31836 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.

Path Traversal in Beego

Also known asGHSA-95f9-94vc-665hGO-2022-0569

Published

Jul 5, 2022

Updated

Oct 28, 2026

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

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

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/beego/beego`	all versions	1.12.11`go get github.com/beego/beego@v1.12.11`
🐹Go	`github.com/beego/beego/v2`	≥ 2.0.0&&< 2.0.4	2.0.4`go get github.com/beego/beego/v2@v2.0.4`

Affected Products

1 product · 1 configurations

Application

beegobeego

≤ 2.0.3

range

Exploits & PoCs

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

The leafInfo.match() function in Beego v2.0.3 and below uses path.join()…

github.comNVDJul 2022

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/beego/beego, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2022-31836 is resolved across your whole dependency graph.
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 CVE-2022-31836 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-22Path Traversal

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Jul 5, 2022

First exploit

Jul 14, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-31836

GHSA-95f9-94vc-665h

GO-2022-0569

References

Advisorygithub.com · CVE 2022 31836.json Advisorygithub.com · GHSA 95f9 94vc 665h Advisorynvd.nist.gov · CVE 2022 31836 Reportgithub.com Webgithub.com Webgithub.com · ea5ae58d40589d249cf577a053e490509de2bf57 Webpkg.go.dev · GO 2022 0569 Packagegithub.com · beego

Related vulnerabilities

This CVE is critical severity; 2 of 8 other CVEs affecting beego are rated as high or higher (top: critical).

CVE-2025-30223CVE-2024-55885CVE-2019-16355CVE-2022-31259CVE-2021-30080CVE-2021-27117CVE-2021-27116CVE-2019-16354

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-31836 — beego

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-31836 in your dependencies?