Elrond-GO processing: fallback search of SCRs when not found in the main cache

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:L

EPSS

• CVE-2022-46173: 0.79% estimated exploitation activity in the next 30 days; percentile 56.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Processing issue, 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. Patches All versions = v1.3.50 will contain this patch Workarounds For the moment there is no workaround References N/A For more information If you have any questions or comments about this advisory: Open an issue in elrond-go main repo

Published by the source

30 Dec 2022, 16:57 UTC

Last modified by the source

30 Jan 2023, 05:06 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p228-4mrh-ww7r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-46173

Advisory: Elrond-GO processing: fallback search of SCRs when not found in the main cache
IDs: CVE-2022-46173, GHSA-p228-4mrh-ww7r
Record: https://patchnext.com/advisories/cve-2022-46173 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ElrondNetwork/elrond-go 1.3.50. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ElrondNetwork/elrond-go: affected <= 1.3.48; fixed in 1.3.50

## Suggested inspection (read-only)
- Go github.com/ElrondNetwork/elrond-go: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ElrondNetwork/elrond-go.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p228-4mrh-ww7r (GitHub-reviewed advisory GHSA-p228-4mrh-ww7r lists affected ranges: Go github.com/ElrondNetwork/elrond-go >=0 <=1.3.48)

Commands are suggestions: review each one before running it.