NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
LOW severity

Hwameistor Potential Permission Leakage of Cluster LevelGHSA-mgwr-h7mv-fh29

LOWFix: hwameistor/hwameistor@edf4ceb

GHSA-mgwr-h7mv-fh29 is a low-severity (CVSS 2.3) Information Exposure vulnerability in github.com/hwameistor/hwameistor. A fix is available for github.com/hwameistor/hwameistor — see the affected versions and patch details below.

Also known asCVE-2024-45054GO-2024-3103
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 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 GHSA-mgwr-h7mv-fh29.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk
0.00%0.25%0.50%0.75%0.1%0.3%0.3%0.3%May 26Oct 26Nov 26

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/hwameistor/hwameistor

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

Impact

What kind of vulnerability is it? Who is impacted? This ClusterRole has * verbs of * resources. If a malicious user can access the worker node which has hwameistor's deployment, he/she can abuse these excessive permissions to do whatever he/she likes to the whole cluster, resulting in a cluster-level privilege escalation.

Patches

Has the problem been patched? What versions should users upgrade to?

= v0.14.6

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading? Update and Limit the ClusterRole using security-role.

References

Are there any links users can visit to find out more? issues: https://github.com/hwameistor/hwameistor/issues/1457 https://github.com/hwameistor/hwameistor/issues/1460

also reported by users via mails: sparkEchooo, younaman

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/hwameistor/hwameistorall versions0.14.6go get github.com/hwameistor/hwameistor@v0.14.6

Affected Products

1 product · 1 configurations
Application
hwameistorhwameistor
< 0.14.6
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update github.com/hwameistor/hwameistor to 0.14.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mgwr-h7mv-fh29 is resolved across your whole dependency graph.

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

### Impact _What kind of vulnerability is it? Who is impacted?_ This ClusterRole has * verbs of * resources. If a malicious user can access the worker node which has hwameistor's deployment, he/she can abuse these excessive permissions to do whatever he/she likes to the whole cluster, resulting in a cluster-level privilege escalation. ### Patches _Has the problem been patched? What versions should users upgrade to?_ >= v0.14.6 ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ Update and Limit the ClusterRole using [security-role](https://gith
O3 Security · Impact-Aware SCA

Is GHSA-mgwr-h7mv-fh29 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Hwameistor Potential Permission Leakage of Cluster Level