# CVE-2026-26267: rs-soroban-sdk #[contractimpl] macro calls inherent function instead of trait function when names collide > A macro bug in the Soroban SDK causes inherent functions to override trait functions, potentially bypassing critical security checks in smart contracts. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 19 Feb 2026 - **Updated:** 19 Feb 2026 - **Also known as:** GHSA-4chv-4c6w-w254 ## 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 `::func()` to `::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 (Always-Incorrect Control Flow Implementation) ## Which versions are affected by CVE-2026-26267? 6 open source packages ship an affected version, including soroban-sdk-macros. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `soroban-sdk-macros` | crates.io | All versions | 22.0.10 | | `soroban-sdk-macros` | crates.io | All versions | 22.0.10 | | `soroban-sdk-macros` | crates.io | From 23.0.0 | 23.5.2 | | `soroban-sdk-macros` | crates.io | From 23.0.0 | 23.5.2 | | `soroban-sdk-macros` | crates.io | From 25.0.0 | 25.1.1 | | `soroban-sdk-macros` | crates.io | From 25.0.0 | 25.1.1 | Products: 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](https://insights.sbomify.com/CVE-2026-32322/): soroban-sdk: `Fr` scalar field equality comparison bypasses modular reduction (medium 5.3) - [CVE-2026-24889](https://insights.sbomify.com/CVE-2026-24889/): soroban-sdk has overflow in Bytes::slice, Vec::slice, GenRange::gen_range for u64 (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-26267 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2026-26267 in the wild and no public exploit code. Affected packages and fixed versions: - soroban-sdk-macros (crates.io): affected all versions; fixed in 22.0.10 - soroban-sdk-macros (crates.io): affected all versions; fixed in 22.0.10 - soroban-sdk-macros (crates.io): affected from 23.0.0; fixed in 23.5.2 - soroban-sdk-macros (crates.io): affected from 23.0.0; fixed in 23.5.2 - soroban-sdk-macros (crates.io): affected from 25.0.0; fixed in 25.1.1 - soroban-sdk-macros (crates.io): affected from 25.0.0; fixed in 25.1.1 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-2026-26267/ (Markdown: https://insights.sbomify.com/CVE-2026-26267/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26267 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26267 - OSV: https://osv.dev/vulnerability/CVE-2026-26267 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-26267/ Summaries are generated and may contain mistakes; the official description above is the record.