How severe is GHSA-fpgj-cr28-fvpx?

No CVSS score has been assigned to GHSA-fpgj-cr28-fvpx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fpgj-cr28-fvpx?

GHSA-fpgj-cr28-fvpx affects the following packages: github.com/CosmWasm/wasmd (Go). Ecosystems affected: Go.

How do I fix GHSA-fpgj-cr28-fvpx?

Update github.com/CosmWasm/wasmd to 0.53.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fpgj-cr28-fvpx is resolved across your whole dependency graph.

How do I detect GHSA-fpgj-cr28-fvpx in my Go dependencies?

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

How do I mitigate GHSA-fpgj-cr28-fvpx 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-fpgj-cr28-fvpx?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fpgj-cr28-fvpx can be triaged on real exposure rather than presence alone.

Is GHSA-fpgj-cr28-fvpx actively exploited in the wild?

No public exploit code has been indexed for GHSA-fpgj-cr28-fvpx 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-fpgj-cr28-fvpx published, and has it been updated?

GHSA-fpgj-cr28-fvpx was published on August 21, 2024 and was last updated on August 30, 2024. 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

GHSA-fpgj-cr28-fvpx — wasmd

Fix: CosmWasm/wasmd@db8981d

GHSA-fpgj-cr28-fvpx is a security vulnerability in github.com/CosmWasm/wasmd. A fix is available for github.com/CosmWasm/wasmd — see the affected versions and patch details below.

CWA-2024-006: wasmd non-deterministic module_query_safe query

Also known asGO-2024-3081

Published

Aug 21, 2024

Updated

Aug 30, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 30, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/CosmWasm/wasmd

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

Component: wasmd Criticality: Medium (ACMv1: I:Moderate; L:Likely) Patched versions: wasmd 0.53.0

See CWA-2024-006 for more details.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/CosmWasm/wasmd`	≥ 0.52.0&&< 0.53.0	0.53.0`go get github.com/CosmWasm/wasmd@v0.53.0`

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/CosmWasm/wasmd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/CosmWasm/wasmd to 0.53.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fpgj-cr28-fvpx 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-fpgj-cr28-fvpx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-fpgj-cr28-fvpx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

**Component:** wasmd **Criticality:** Medium ([ACMv1](https://github.com/interchainio/security/blob/main/resources/CLASSIFICATION_MATRIX.md): I:Moderate; L:Likely) **Patched versions:** wasmd 0.53.0 See [CWA-2024-006](https://github.com/CosmWasm/advisories/blob/main/CWAs/CWA-2024-006.md) for more details.

O3 Security · Impact-Aware SCA

Is GHSA-fpgj-cr28-fvpx in your dependencies?

O3 Security finds GHSA-fpgj-cr28-fvpx across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works