CVE-2026-26267

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-26267", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-02-12T17:10:53.412Z", "datePublished": "2026-02-19T19:35:40.539Z", "dateUpdated": "2026-02-19T21:22:10.126Z"}, "containers": {"cna": {"title": "rs-soroban-sdk #[contractimpl] macro calls inherent function instead of trait function when names collide", "problemTypes": [{"descriptions": [{"cweId": "CWE-670", "lang": "en", "description": "CWE-670: Always-Incorrect Control Flow Implementation", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "version": "3.1"}}], "references": [{"name": "https://github.com/stellar/rs-soroban-sdk/security/advisories/GHSA-4chv-4c6w-w254", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/stellar/rs-soroban-sdk/security/advisories/GHSA-4chv-4c6w-w254"}, {"name": "https://github.com/stellar/rs-soroban-sdk/pull/1729", "tags": ["x_refsource_MISC"], "url": "https://github.com/stellar/rs-soroban-sdk/pull/1729"}, {"name": "https://github.com/stellar/rs-soroban-sdk/pull/1730", "tags": ["x_refsource_MISC"], "url": "https://github.com/stellar/rs-soroban-sdk/pull/1730"}, {"name": "https://github.com/stellar/rs-soroban-sdk/pull/1731", "tags": ["x_refsource_MISC"], "url": "https://github.com/stellar/rs-soroban-sdk/pull/1731"}, {"name": "https://github.com/stellar/rs-soroban-sdk/commit/e92a3933e5f92dc09da3c740cf6a360d55709a2b", "tags": ["x_refsource_MISC"], "url": "https://github.com/stellar/rs-soroban-sdk/commit/e92a3933e5f92dc09da3c740cf6a360d55709a2b"}], "affected": [{"vendor": "stellar", "product": "rs-soroban-sdk", "versions": [{"version": ">= 25.0.0, < 25.1.1", "status": "affected"}, {"version": ">= 23.0.0, < 23.5.2", "status": "affected"}, {"version": "< 22.0.10", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-02-19T19:35:40.539Z"}, "descriptions": [{"lang": "en", "value": "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."}], "source": {"advisory": "GHSA-4chv-4c6w-w254", "discovery": "UNKNOWN"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-02-19T20:58:43.298688Z", "id": "CVE-2026-26267", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-02-19T21:22:10.126Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-26267", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2026-02-19T20:58:43.298688Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-02-19T20:58:44.801Z"}}], "cna": {"title": "rs-soroban-sdk #[contractimpl] macro calls inherent function instead of trait function when names collide", "source": {"advisory": "GHSA-4chv-4c6w-w254", "discovery": "UNKNOWN"}, "metrics": [{"cvssV3_1": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}}], "affected": [{"vendor": "stellar", "product": "rs-soroban-sdk", "versions": [{"status": "affected", "version": ">= 25.0.0, < 25.1.1"}, {"status": "affected", "version": ">= 23.0.0, < 23.5.2"}, {"status": "affected", "version": "< 22.0.10"}]}], "references": [{"url": "https://github.com/stellar/rs-soroban-sdk/security/advisories/GHSA-4chv-4c6w-w254", "name": "https://github.com/stellar/rs-soroban-sdk/security/advisories/GHSA-4chv-4c6w-w254", "tags": ["x_refsource_CONFIRM"]}, {"url": "https://github.com/stellar/rs-soroban-sdk/pull/1729", "name": "https://github.com/stellar/rs-soroban-sdk/pull/1729", "tags": ["x_refsource_MISC"]}, {"url": "https://github.com/stellar/rs-soroban-sdk/pull/1730", "name": "https://github.com/stellar/rs-soroban-sdk/pull/1730", "tags": ["x_refsource_MISC"]}, {"url": "https://github.com/stellar/rs-soroban-sdk/pull/1731", "name": "https://github.com/stellar/rs-soroban-sdk/pull/1731", "tags": ["x_refsource_MISC"]}, {"url": "https://github.com/stellar/rs-soroban-sdk/commit/e92a3933e5f92dc09da3c740cf6a360d55709a2b", "name": "https://github.com/stellar/rs-soroban-sdk/commit/e92a3933e5f92dc09da3c740cf6a360d55709a2b", "tags": ["x_refsource_MISC"]}], "descriptions": [{"lang": "en", "value": "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."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-670", "description": "CWE-670: Always-Incorrect Control Flow Implementation"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-02-19T19:35:40.539Z"}}}, "cveMetadata": {"cveId": "CVE-2026-26267", "state": "PUBLISHED", "dateUpdated": "2026-02-19T21:22:10.126Z", "dateReserved": "2026-02-12T17:10:53.412Z", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "datePublished": "2026-02-19T19:35:40.539Z", "assignerShortName": "GitHub_M"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"product": "rs-soroban-sdk", "vendor": "stellar", "versions": [{"status": "affected", "version": ">= 25.0.0, < 25.1.1"}, {"status": "affected", "version": ">= 23.0.0, < 23.5.2"}, {"status": "affected", "version": "< 22.0.10"}]}], "source": "security-advisories@github.com"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:stellar:rs-soroban-sdk:*:*:*:*:*:rust:*:*", "matchCriteriaId": "05CB12AE-79C0-4E3E-A5DA-B7B4ADF1D6AF", "versionEndExcluding": "22.0.10", "vulnerable": true}, {"criteria": "cpe:2.3:a:stellar:rs-soroban-sdk:*:*:*:*:*:rust:*:*", "matchCriteriaId": "7C4E14BA-C772-46BA-BC92-02A07FB8B574", "versionEndExcluding": "23.5.2", "versionStartIncluding": "23.0.0", "vulnerable": true}, {"criteria": "cpe:2.3:a:stellar:rs-soroban-sdk:*:*:*:*:*:rust:*:*", "matchCriteriaId": "AC7DFEC6-FCA8-4319-AB18-85B0E972DD1C", "versionEndExcluding": "25.1.1", "versionStartIncluding": "25.0.0", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "soroban-sdk es un SDK de Rust para contratos Soroban. Antes de las versiones 22.0.10, 23.5.2 y 25.1.1, la macro `#[contractimpl]` contiene un error en c\u00f3mo conecta las llamadas a funciones. `#[contractimpl]` genera c\u00f3digo que utiliza llamadas al estilo `MyContract::value()` incluso cuando est\u00e1 procesando la versi\u00f3n del trait. Esto significa que si una funci\u00f3n inherente tambi\u00e9n se define con el mismo nombre, se llama a la funci\u00f3n inherente en lugar de la funci\u00f3n del trait. Esto significa que el punto de entrada exportado por Wasm llama silenciosamente a la funci\u00f3n incorrecta cuando se cumplen dos condiciones simult\u00e1neamente: Primero, se define un bloque `impl Trait for MyContract` con una o m\u00e1s funciones, con `#[contractimpl]` aplicado. Segundo, se define un bloque `impl MyContract` con una o m\u00e1s funciones con nombres id\u00e9nticos, sin `#[contractimpl]` aplicado. Si la versi\u00f3n del trait contiene comprobaciones de seguridad importantes, como verificar que el llamador est\u00e1 autorizado, que la versi\u00f3n inherente no tiene, esas comprobaciones se eluden. Cualquiera que interact\u00fae con el contrato a trav\u00e9s de su interfaz p\u00fablica llamar\u00e1 a la funci\u00f3n incorrecta. El problema est\u00e1 parcheado en las versiones de `soroban-sdk-macros` 22.0.10, 23.5.2 y 25.1.1. La correcci\u00f3n cambia la llamada generada de `::func()` a `::func()` al procesar implementaciones de traits, asegurando que Rust resuelva a la funci\u00f3n asociada del trait independientemente de si existe una funci\u00f3n inherente con el mismo nombre. Los usuarios deben actualizar a `soroban-sdk-macros` 22.0.10, 23.5.2 o 25.1.1 y recompilar sus contratos. Si la actualizaci\u00f3n no es posible de inmediato, los desarrolladores de contratos pueden evitar el problema asegur\u00e1ndose de que ninguna funci\u00f3n asociada inherente en el tipo de contrato comparta un nombre con ninguna funci\u00f3n en la implementaci\u00f3n del trait. Renombrar o eliminar la funci\u00f3n inherente en conflicto elimina la ambig\u00fcedad y hace que el c\u00f3digo generado por la macro se resuelva correctamente a la funci\u00f3n del trait."}], "id": "CVE-2026-26267", "lastModified": "2026-06-17T10:26:00.800", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 3.6, "source": "security-advisories@github.com", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-26267", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2026-02-19T20:58:43.298688Z", "version": "2.0.3"}}]}, "published": "2026-02-19T20:25:43.530", "references": [{"source": "security-advisories@github.com", "tags": ["Patch"], "url": "https://github.com/stellar/rs-soroban-sdk/commit/e92a3933e5f92dc09da3c740cf6a360d55709a2b"}, {"source": "security-advisories@github.com", "tags": ["Issue Tracking", "Patch"], "url": "https://github.com/stellar/rs-soroban-sdk/pull/1729"}, {"source": "security-advisories@github.com", "tags": ["Issue Tracking", "Patch"], "url": "https://github.com/stellar/rs-soroban-sdk/pull/1730"}, {"source": "security-advisories@github.com", "tags": ["Issue Tracking", "Patch"], "url": "https://github.com/stellar/rs-soroban-sdk/pull/1731"}, {"source": "security-advisories@github.com", "tags": ["Exploit", "Patch", "Vendor Advisory"], "url": "https://github.com/stellar/rs-soroban-sdk/security/advisories/GHSA-4chv-4c6w-w254"}], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-670"}], "source": "security-advisories@github.com", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[25.0.0,25.1.1)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[23.0.0,23.5.2)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[0,22.0.10)"}}], "enrichment": {"confidence": 100.0, "confidence_source": "matching", "scores": [{"score": 100.0, "source": "matching"}]}, "original": {"product": "rs-soroban-sdk", "source": "cna", "vendor": "stellar"}, "product": "rs-soroban-sdk", "vendor": "stellar"}], "analysis": {"en": {"generated_at": "2026-04-18T11:44:34.335037+00:00", "value": {"mitigation_remediation": ["Upgrade your projects to soroban-sdk-macros v22.0.10, 23.5.2, or 25.1.1 and recompile all smart contracts.", "Regenerate the SDK\u2019s derived code to ensure the new version uses trait-aware function resolution.", "As a temporary measure, audit your contracts for inherent methods that share names with trait functions and rename or remove those inherent methods to eliminate the ambiguity until the patch is applied."], "summary": {"action": "Immediate Patch", "impact": "Authorization Bypass"}, "threat_synthesis": {"affected_systems": "The vulnerability affects the Stellar rs\u2011soroban\u2011sdk, specifically all builds prior to macros versions 22.0.10, 23.5.2, and 25.1.1. Users compiling contracts with these earlier SDK releases are impacted.", "description_and_impact": "The Soroban Rust SDK contains a macro bug that incorrectly routes contract calls. When a contract implements a trait with #[contractimpl] and also has an inherent method of the same name, the generated code mistakenly calls the inherent method instead of the trait method. If the trait method contains essential security checks such as caller verification, those checks are bypassed, allowing unauthenticated users to trigger functions that should be protected. This flaw effectively removes a layer of authorization and can lead to unauthorized state changes or other unintended contract behavior.", "risk_and_exploitability": "The CVSS score of 7.5 reflects a high impact from an information\u2011system perspective, while the EPSS score of less than 1% indicates a low probability of exploitation in the wild at present. The vulnerability is not listed in the CISA KEV catalog, suggesting no known active exploitation. Attackers can trigger the flaw through the standard WASM contract interface over the network, exploiting the incorrect dispatch when trait\u2011based and inherent methods collide."}}}}, "created": "2026-02-20T09:54:12.437524+00:00", "updated": "2026-04-18T11:45:44.601744+00:00", "vendors": ["stellar", "stellar$PRODUCT$rs-soroban-sdk"]}