Skip to main content
No exploitation reportedFix available

CVE-2022-46173

No exploitation reported by the sources we read.

  • Published2022-12-28
  • Fixed in1.3.50
  • WeaknessCWE-669

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2022-12-2807:15CVE publishedNVD

Versions per branch

NVD · OSV
Elrond elrond go
BranchAffectedFixed in
1.3< 1.3.501.3.50

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • ElrondNetwork elrond-go
    Affected
    • = < 1.3.50no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2022-12-28

Fix

  1. Update Elrond elrond go to 1.3.50

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2025-04-11
  • CNACVSS 3.17.2known since 2026-10-23
  • NVDCVSS 3.16.5read 2026-10-23
  • CNAweakness (CWE)CWE-669known since 2026-10-23
  • FIRST EPSSEPSS score0.8 %2026-11-18
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2022-12-30

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Published
2022-12-28
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-p228-4mrh-ww7r

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.

Is CVE-2022-46173 actively exploited?

Active exploitation of CVE-2022-46173 has not been confirmed. Its EPSS score was 0.8% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-46173?

CVE-2022-46173 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L.

Running ElrondNetwork/elrond-go? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record