How severe is GHSA-w44m-8mv2-v78h?

No CVSS score has been assigned to GHSA-w44m-8mv2-v78h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w44m-8mv2-v78h?

GHSA-w44m-8mv2-v78h affects the following packages: github.com/cosmos/cosmos-sdk (Go), github.com/cosmos/cosmos-sdk (Go). Ecosystems affected: Go.

How do I fix GHSA-w44m-8mv2-v78h?

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-w44m-8mv2-v78h is resolved across your whole dependency graph.

How do I detect GHSA-w44m-8mv2-v78h in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cosmos/cosmos-sdk. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-w44m-8mv2-v78h if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-w44m-8mv2-v78h?

O3 pinpoints whether GHSA-w44m-8mv2-v78h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-w44m-8mv2-v78h actively exploited in the wild?

No public exploit code has been indexed for GHSA-w44m-8mv2-v78h 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.

When was GHSA-w44m-8mv2-v78h published, and has it been updated?

GHSA-w44m-8mv2-v78h was published on June 22, 2023 and was last updated on May 7, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Withdrawn — this advisory has been retracted

🐹 Go

GHSA-w44m-8mv2-v78h

Duplicate Advisory: Cosmos "Barberry" vulnerability in github.com/cosmos/cosmos-sdk

Also known asGHSA-j2cr-jc39-wpx5GO-2023-1861

Published

Jun 22, 2023

Updated

May 7, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐹github.com/cosmos/cosmos-sdk🐹github.com/cosmos/cosmos-sdk

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

Withdrawn

This advisory has been withdrawn because it is a duplicate of GHSA-j2cr-jc39-wpx5. This link is maintained to preserve external references.

Original Description

The cosmos-sdk module is affected by the vulnerability codenamed "Barberry".

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/cosmos/cosmos-sdk`	≥ 0.46.0&&< 0.46.13	0.46.13
🐹Go	`github.com/cosmos/cosmos-sdk`	≥ 0.47.0&&< 0.47.3	0.47.3

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/cosmos/cosmos-sdk. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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-w44m-8mv2-v78h 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 pinpoints whether GHSA-w44m-8mv2-v78h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-w44m-8mv2-v78h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Withdrawn This advisory has been withdrawn because it is a duplicate of GHSA-j2cr-jc39-wpx5. This link is maintained to preserve external references. ## Original Description The cosmos-sdk module is affected by the vulnerability codenamed "Barberry".

O3 Security · Impact-Aware SCA

Is GHSA-w44m-8mv2-v78h in your dependencies?

O3 detects GHSA-w44m-8mv2-v78h across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works