# CVE-2022-36061: Elrond go can execute on same context checks in VM

> Attackers can modify smart contract state via read-only calls, bypassing intended immutability constraints in the Elrond network.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Sep 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-mv8x-668m-53fg, GO-2022-0971

## What is CVE-2022-36061?

CVE-2022-36061 is a medium-severity vulnerability in ElrondNetwork elrond-go, published on 6 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Elrond go is the go implementation for the Elrond Network protocol. In versions prior to 1.3.35, read only calls between contracts can generate smart contracts results. For example, if contract A calls in read only mode contract B and the called function will make changes upon the contract's B state, the state will be altered for contract B as if the call was not made in the read-only mode. This can lead to some effects not designed by the original smart contracts programmers. This issue was patched in version 1.3.35. There are no known workarounds.

Weakness: CWE-665 (Improper Initialization)

## Which versions are affected by CVE-2022-36061?

3 open source packages ship an affected version, including github.com/ElrondNetwork/elrond-go. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ElrondNetwork/elrond-go` | Go | All versions | 1.3.35 |
| `github.com/ElrondNetwork/elrond-go` | Go | All versions | 1.3.35 |
| `github.com/ElrondNetwork/elrond-go` | Go | All versions | 1.3.35 |

Products: Elrond Elrond Go.

## How do I fix CVE-2022-36061?

Upgrade github.com/ElrondNetwork/elrond-go to 1.3.35 or later.

## Is CVE-2022-36061 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36061 exists.

## Other vulnerabilities in ElrondNetwork elrond-go

- [CVE-2022-36058](https://insights.sbomify.com/CVE-2022-36058/): elrond-go MultiESDTNFTTransfer call on a SC address with missing function name (high 7.5)
- [CVE-2022-46173](https://insights.sbomify.com/CVE-2022-46173/): Elrond go Processing: fallback search of SCRs when not found in the main cache (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36061 and fix it if it is affected.

What it is: CVE-2022-36061 is a medium-severity vulnerability in ElrondNetwork elrond-go, published on 6 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36061 exists.

Affected packages and fixed versions:
- github.com/ElrondNetwork/elrond-go (Go): affected all versions; fixed in 1.3.35
- github.com/ElrondNetwork/elrond-go (Go): affected all versions; fixed in 1.3.35
- github.com/ElrondNetwork/elrond-go (Go): affected all versions; fixed in 1.3.35

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-36061/ (Markdown: https://insights.sbomify.com/CVE-2022-36061/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-36061
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-36061
- OSV: https://osv.dev/vulnerability/CVE-2022-36061

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-36061/
Summaries are generated and may contain mistakes; the official description above is the record.