GHSA-j2cr-jc39-wpx5 — cosmos-sdk
Fix: cosmos/cosmos-sdk#16466GHSA-j2cr-jc39-wpx5 is a security vulnerability in github.com/cosmos/cosmos-sdk. A fix is available for github.com/cosmos/cosmos-sdk — see the affected versions and patch details below.
Barberry Security Advisory - regarding x/auth periodic vesting accounts
Real-World Exposure
github.com/cosmos/cosmos-sdk🐹github.com/cosmos/cosmos-sdkReal-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
In PeriodicVestingAccount, defined in x/auth, an attacker can initialize a victim's account as a malicious vesting account, which allows deposits but does not allow withdrawals. When the user then deposits funds into their account, those funds are locked forever, and the user is not able to withdraw them.
Patches
>= v0.46.13 for Cosmos SDK v0.46.x >= v0.47.3 for Cosmos SDK v0.47.x
If a network backported periodic vesting accounts to earlier versions of the SDK, those networks are affected too.
Workarounds
There is no workaround for this issue. Upgrade immediately.
References
- Patched versions release notes: v0.47.3, v0.46.13.
- Forum Post
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/cosmos/cosmos-sdk | ≥ 0.46.0&&< 0.46.13 | 0.46.13go get github.com/cosmos/cosmos-sdk@v0.46.13 |
| 🐹Go | github.com/cosmos/cosmos-sdk | ≥ 0.47.0&&< 0.47.3 | 0.47.3go get github.com/cosmos/cosmos-sdk@v0.47.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cosmos/cosmos-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cosmos/cosmos-sdk to 0.46.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j2cr-jc39-wpx5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-j2cr-jc39-wpx5 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-j2cr-jc39-wpx5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-j2cr-jc39-wpx5 in your dependencies?
O3 Security finds GHSA-j2cr-jc39-wpx5 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.