A HIGH-severity vulnerability identified as CVE-2026-26267 has been published on February 19, 2026 with a CVSS base score of 7.5. The vulnerability affects Stellar Rs-soroban-sdk. This security advisory provides a detailed breakdown of the vulnerability, its potential impact, weakness classification, and actionable steps to protect your systems.
Vulnerability Details
CVE ID: CVE-2026-26267
Severity: HIGH
CVSS Score: 7.5
Published: February 19, 2026
Affected Product: Stellar Rs-soroban-sdk
Weakness (CWE): CWE-670
| Attack Vector | Network |
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | None |
| Confidentiality Impact | None |
| Integrity Impact | High |
| Availability Impact | None |
Technical 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.
Potential Impact
If exploited, this high-severity vulnerability could allow an attacker to tamper with system integrity. Organizations running Stellar Rs-soroban-sdk should treat this as a priority remediation item.
Recommended Action
A patch or vendor advisory is available. Take the following steps immediately:
- Review the vendor advisory linked in the References section below.
- Identify all instances of the affected software in your environment.
- Apply the available patch or upgrade to the fixed version as soon as possible.
- If patching is not immediately possible, implement compensating controls such as WAF rules, network segmentation, or disabling the affected feature.
- Monitor your systems for signs of exploitation using your SIEM or IDS/IPS.
References
Related Security Advisories
- [HIGH] CVE-2026-27464 — CVSS 7.7 (February 21, 2026) — HIGH / CVSS 7.7
- [HIGH] CVE-2026-27466 — CVSS 7.2 (February 21, 2026) — HIGH / CVSS 7.2
- [HIGH] CVE-2026-26050 — CVSS 7.8 (February 20, 2026) — HIGH / CVSS 7.8
![[CRITICAL] CVE-2026-28773 — CVSS 9.3 (March 4, 2026)](https://atlas-cybersecurity.com/wp-content/plugins/elementor/assets/images/placeholder.png)
