CVE-2026-26267

HIGH EPSS 23.4%
Published Feb 19, 20264mo ago · Modified Jun 17, 20262w ago
7.5 CVSS 3.1
High
Find Similar
Published Feb 19, 2026 4mo ago
Last Modified Jun 17, 2026 2w ago

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.

CVSS Details

Base Score
7.5
Exploitability
3.9
Impact
3.6
Vector string
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Attack Vector Network
Attack Complexity Low
Privileges Required None
User Interaction None
Scope Unchanged
Confidentiality None
Integrity High
Availability None

Threat Intelligence

EPSS Exploit Probability
23.4% percentile
Exploit & Patch Status
Public Exploit Known
Patch Available

Weaknesses 1

CWE-670

Affected Products 3

VendorProductVersionRange
stellarrs-soroban-sdk* <22.0.10
stellarrs-soroban-sdk*≥23.0.0  –  <23.5.2
stellarrs-soroban-sdk*≥25.0.0  –  <25.1.1

References 5

  • github.com https://github.com/stellar/rs-soroban-sdk/commit/e92a3933e5f92dc09da3c740cf6a360d55709a2b
    Patch
  • github.com https://github.com/stellar/rs-soroban-sdk/pull/1729
    Issue TrackingPatch
  • github.com https://github.com/stellar/rs-soroban-sdk/pull/1730
    Issue TrackingPatch
  • github.com https://github.com/stellar/rs-soroban-sdk/pull/1731
    Issue TrackingPatch
  • github.com https://github.com/stellar/rs-soroban-sdk/security/advisories/GHSA-4chv-4c6w-w254
    ExploitPatchVendor Advisory

Remediation

  • github.com https://github.com/stellar/rs-soroban-sdk/commit/e92a3933e5f92dc09da3c740cf6a360d55709a2b
    Patch
  • github.com https://github.com/stellar/rs-soroban-sdk/pull/1729
    Issue TrackingPatch
  • github.com https://github.com/stellar/rs-soroban-sdk/pull/1730
    Issue TrackingPatch
  • github.com https://github.com/stellar/rs-soroban-sdk/pull/1731
    Issue TrackingPatch
  • github.com https://github.com/stellar/rs-soroban-sdk/security/advisories/GHSA-4chv-4c6w-w254
    ExploitPatchVendor Advisory