CVE-2026-26267 rs-soroban-sdk #[contractimpl] macro calls inherent function instead of trait function when names collide

What is CVE-2026-26267?

CVE-2026-26267 is a high-severity vulnerability in stellar rs-soroban-sdk, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

soroban-sdk is a Rust SDK for Soroban contracts. Prior to versions 22.0.10, 23.5.2, and 25.1.1, the `#[contractimpl]` macro contains a bug in how it wires up function calls. `#[contractimpl]` generates code that uses `MyContract::value()` style calls even when it's processing the trait version. This means if an inherent function is also defined with the same name, the inherent function gets called instead of the trait function. This means the Wasm-exported entry point silently calls the wrong function when two conditions are met simultaneously: First, an `impl Trait for MyContract` block is defined with one or more functions, with `#[contractimpl]` applied. Second, an `impl MyContract` block is defined with one or more identically named functions, without `#[contractimpl]` applied. If the trait version contains important security checks, such as verifying the caller is authorized, that the inherent version does not, those checks are bypassed. Anyone interacting with the contract through its public interface will call the wrong function. The problem is patched in `soroban-sdk-macros` versions 22.0.10, 23.5.2, and 25.1.1. The fix changes the generated call from `<Type>::func()` to `<Type as Trait>::func()` when processing trait implementations, ensuring Rust resolves to the trait associated function regardless of whether an inherent function with the same name exists. Users should upgrade to `soroban-sdk-macros` 22.0.10, 23.5.2, or 25.1.1 and recompile their contracts. If upgrading is not immediately possible, contract developers can avoid the issue by ensuring that no inherent associated function on the contract type shares a name with any function in the trait implementation. Renaming or removing the conflicting inherent function eliminates the ambiguity and causes the macro-generated code to correctly resolve to the trait function.

Weakness: CWE-670

Which versions are affected by CVE-2026-26267?

6 open source packages ship an affected version, including soroban-sdk-macros. It affects 1 product.

Products include Stellar Rs-Soroban-Sdk.

How do I fix CVE-2026-26267?

Upgrade soroban-sdk-macros to a fixed version for your release line: 22.0.10, 23.5.2 or 25.1.1.

Is CVE-2026-26267 being exploited?

There is no known exploitation of CVE-2026-26267 in the wild and no public exploit code.

Other vulnerabilities in stellar rs-soroban-sdk

• CVE-2026-32322 soroban-sdk: `Fr` scalar field equality comparison bypasses modular reduction Medium 5.3
• CVE-2026-24889 soroban-sdk has overflow in Bytes::slice, Vec::slice, GenRange::gen_range for u64 Medium 5.3

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-4chv-4c6w-w254.