How severe is CVE-2022-29180?

CVE-2022-29180 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-29180?

CVE-2022-29180 affects the following packages: github.com/charmbracelet/charm (Go). Ecosystems affected: Go.

How do I fix CVE-2022-29180?

Update github.com/charmbracelet/charm to 0.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-29180 is resolved across your whole dependency graph.

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

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

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

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

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

No public exploit code has been indexed for CVE-2022-29180 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 CVE-2022-29180?

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

CVE-2022-29180 is classified as Server-Side Request Forgery (SSRF) (CWE-918). 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-29180 published, and has it been updated?

CVE-2022-29180 was published on May 7, 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

MEDIUM severity

CVE-2022-29180 — charm

MEDIUMFix: charmbracelet/charm@3c90668

CVE-2022-29180 is a medium-severity (CVSS 5.9) Server-Side Request Forgery (SSRF) vulnerability in github.com/charmbracelet/charm. A fix is available for github.com/charmbracelet/charm — see the affected versions and patch details below.

Charm vulnerable to server-side request forgery (SSRF)

Also known asGHSA-4wpp-w5r4-7v5vGO-2022-0449

Published

May 7, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-29180.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% 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

1 pkg affected

🐹github.com/charmbracelet/charm

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

We've discovered a vulnerability in which attackers could forge HTTP requests to manipulate the charm data directory to access or delete anything on the server. This has been patched in https://github.com/charmbracelet/charm/commit/3c90668f955c7ce5ef721e4fc9faee7053232fd3 and is available in release v0.12.1. We recommend that all users running self-hosted charm instances update immediately.

This vulnerability was found in-house and we haven't been notified of any potential exploiters.

Additional notes

Encrypted user data uploaded to the Charm server is safe as Charm servers cannot decrypt user data. This includes filenames, paths, and all key-value data.
Users running the official Charm Docker images are at minimal risk because the exploit is limited to the containerized filesystem.

For more information

If you have any questions or comments about this advisory:

Open a discussion
Email us at [email protected]
Chat with us on Slack

Charm热爱开源 • Charm loves open source

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/charmbracelet/charm`	≥ 0.9.0&&< 0.12.1	0.12.1`go get github.com/charmbracelet/charm@v0.12.1`

Affected Products

1 product · 1 configurations

Application

charmcharm

≥ 0.9.0 && < 0.12.1

range

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/charmbracelet/charm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/charmbracelet/charm to 0.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-29180 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

We've discovered a vulnerability in which attackers could forge HTTP requests to manipulate the `charm` data directory to access or delete anything on the server. This has been patched in https://github.com/charmbracelet/charm/commit/3c90668f955c7ce5ef721e4fc9faee7053232fd3 and is available in release [v0.12.1](https://github.com/charmbracelet/charm/releases/tag/v0.12.1). We recommend that all users running self-hosted `charm` instances update immediately. This vulnerability was found in-house and we haven't been notified of any potential exploiters. ### Additional notes * Encrypted user da

O3 Security · Impact-Aware SCA

Is CVE-2022-29180 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.9/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

May 7, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-29180

GHSA-4wpp-w5r4-7v5v

GO-2022-0449

References

Advisorygithub.com · CVE 2022 29180.json Advisorygithub.com · GHSA 4wpp w5r4 7v5v Advisorynvd.nist.gov · CVE 2022 29180 Fixgithub.com · 3c90668f955c7ce5ef721e4fc9faee7053232fd3 Packagegithub.com · charm

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-918 are rated as high or higher (top: high).

CVE-2026-28385GHSA-7wpf-ch8f-5f4xCVE-2026-54442GHSA-4mfg-r38w-w8fgCVE-2026-118660CVE-2026-108360CVE-2026-114609CVE-2026-116686Browse all CWE-918

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026