Server-Side Request Forgery in charm

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2022-29180: 0.80% estimated exploitation activity in the next 30 days; percentile 56.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 vt100@charm.sh Chat with us on Slack <a href="https://charm.sh/"<img alt="the Charm logo"…

Published by the source

24 May 2022, 20:55 UTC

Last modified by the source

27 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4wpp-w5r4-7v5v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-29180

Advisory: Server-Side Request Forgery in charm
IDs: CVE-2022-29180, GHSA-4wpp-w5r4-7v5v
Record: https://patchnext.com/advisories/cve-2022-29180 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/charmbracelet/charm 0.12.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/charmbracelet/charm: affected >= 0.9.0, < 0.12.1; fixed in 0.12.1

## Suggested inspection (read-only)
- Go github.com/charmbracelet/charm: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/charmbracelet/charm.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4wpp-w5r4-7v5v (GitHub-reviewed advisory GHSA-4wpp-w5r4-7v5v lists affected ranges: Go github.com/charmbracelet/charm >=0.9.0 <0.12.1)

Commands are suggestions: review each one before running it.