How severe is CVE-2022-46173?

CVE-2022-46173 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability low.

Is CVE-2022-46173 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-46173?

CVE-2022-46173 affects Elrond Elrond Go. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-46173?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2022-46173 published?

CVE-2022-46173 was published on 2022-12-28 and last updated on 2026-06-17.

CVE-2022-46173

CVE-2022-46173 is a high-severity vulnerability in Elrond Elrond Go with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-669.

Key facts

Severity: High (CVSS 3.x base score 7.2)
EPSS exploit prediction: 1% (50th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-669
Affected product: Elrond Elrond Go
Published: 2022-12-28
Last modified: 2026-06-17

Description

Elrond-GO is a go implementation for the Elrond Network protocol. Versions prior to 1.3.50 are subject to a processing issue where nodes are affected when trying to process a cross-shard relayed transaction with a smart contract deploy transaction data. The problem was a bad correlation between the transaction caches and the processing component. If the above-mentioned transaction was sent with more gas than required, the smart contract result (SCR transaction) that should have returned the leftover gas, would have been wrongly added to a cache that the processing unit did not consider. The node stopped notarizing metachain blocks. The fix was actually to extend the SCR transaction search in all other caches if it wasn't found in the correct (expected) sharded-cache. There are no known workarounds at this time. This issue has been patched in version 1.3.50.

Frequently asked questions

What is CVE-2022-46173?: Elrond-GO is a go implementation for the Elrond Network protocol. Versions prior to 1.3.50 are subject to a processing issue where nodes are affected when trying to process a cross-shard relayed transaction with a smart contract deploy transaction data. The problem was a bad correlation between the transaction caches and the processing component. If the above-mentioned transaction was sent with more gas than required, the smart contract result (SCR transaction) that should have returned the leftover gas, would have been wrongly added to a cache that the processing unit did not consider. The node stopped notarizing metachain blocks. The fix was actually to extend the SCR transaction search in all other caches if it wasn't found in the correct (expected) sharded-cache. There are no known workarounds at this time. This issue has been patched in version 1.3.50.
How severe is CVE-2022-46173?: CVE-2022-46173 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability low.
Is CVE-2022-46173 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-46173?: CVE-2022-46173 affects Elrond Elrond Go. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-46173?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-46173 published?: CVE-2022-46173 was published on 2022-12-28 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:elrond:elrond_go:*:*:*:*:*:*:*:*

More vulnerabilities in Elrond Elrond Go

CVE-2022-36058 — High (CVSS 7.5): Elrond go is the go implementation for the Elrond Network protocol. In versions prior to 1.3.34, anyone who uses…
CVE-2022-36061 — Medium (CVSS 6.5): Elrond go is the go implementation for the Elrond Network protocol. In versions prior to 1.3.35, read only calls…

All CVEs affecting Elrond Elrond Go →

Other CWE-669 vulnerabilities

CVE-2021-30120 — Critical (CVSS 9.9): Kaseya VSA before 9.5.7 allows attackers to bypass the 2FA requirement. The need to use 2FA for authentication in…
CVE-2025-67895 — Critical (CVSS 9.8): Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if you…
CVE-2022-4446 — Critical (CVSS 9.8): PHP Remote File Inclusion in GitHub repository tsolucio/corebos prior to 8.0.
CVE-2020-24683 — Critical (CVSS 9.8): The affected versions of S+ Operations (version 2.1 SP1 and earlier) used an approach for user authentication which…
CVE-2020-5800 — Critical (CVSS 9.8): The Eat Spray Love mobile app for both iOS and Android contains logic that allows users to bypass authentication and…
CVE-2020-15892 — Critical (CVSS 9.8): An issue was discovered in apply.cgi on D-Link DAP-1520 devices before 1.10b04Beta02. Whenever a user performs a login…

Browse all CWE-669 vulnerabilities →