ink! vulnerable to incorrect decoding of storage value when using `DelegateCall`

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0097, the 61st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

1. 31 Oct 2026, 15:17 UTC First seen by agentprime
2. 31 Oct 2026, 15:17 UTC Confirmed by OSV

Sources

• GitHub Advisory Database: GHSA-853p-5678-hv8f
• OSV: GHSA-853p-5678-hv8f
• github.com/paritytech/ink/security/advisories/GHSA-853p-5678-hv8f
• nvd.nist.gov/vuln/detail/CVE-2023-34449
• github.com/paritytech/ink/pull/1450
• github.com/paritytech/ink/commit/f1407ee9f87e5f64d467a22d26ee88f61db7f3db
• docs.rs/ink_env/4.2.0/ink_env/call/struct.CallBuilder.html#method.delegate
• docs.rs/ink_env/4.2.0/ink_env/fn.invoke_contract_delegate.html
• github.com/paritytech/ink

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.