CVE-2026-24889

{"id": "CVE-2026-24889", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-24889", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-01-29T16:01:43.687365Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "stellar", "product": "rs-soroban-sdk", "versions": [{"status": "affected", "version": "< 22.0.9"}, {"status": "affected", "version": ">= 23.0.0, < 23.5.1"}, {"status": "affected", "version": ">= 25.0.0, < 25.0.2"}]}]}], "published": "2026-01-28T22:15:56.700", "references": [{"url": "https://github.com/stellar/rs-soroban-sdk/commit/3890521426d71bb4d892b21f5a283a1e836cfa38", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/stellar/rs-soroban-sdk/commit/59fcef437260ed4da42d1efb357137a5c166c02e", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/stellar/rs-soroban-sdk/commit/c2757c6d774dbb28b34a0b77ffe282e59f0f8462", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/stellar/rs-soroban-sdk/pull/1703", "tags": ["Issue Tracking", "Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/stellar/rs-soroban-sdk/releases/tag/v22.0.9", "tags": ["Product", "Release Notes"], "source": "security-advisories@github.com"}, {"url": "https://github.com/stellar/rs-soroban-sdk/releases/tag/v23.5.1", "tags": ["Product", "Release Notes"], "source": "security-advisories@github.com"}, {"url": "https://github.com/stellar/rs-soroban-sdk/releases/tag/v25.0.2", "tags": ["Product", "Release Notes"], "source": "security-advisories@github.com"}, {"url": "https://github.com/stellar/rs-soroban-sdk/security/advisories/GHSA-96xm-fv9w-pf3f", "tags": ["Mitigation", "Patch", "Vendor Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-190"}]}], "descriptions": [{"lang": "en", "value": "soroban-sdk is a Rust SDK for Soroban contracts. Arithmetic overflow can be triggered in the `Bytes::slice`, `Vec::slice`, and `Prng::gen_range` (for `u64`) methods in the `soroban-sdk` in versions up to and including `25.0.1`, `23.5.1`, and `25.0.2`. Contracts that pass user-controlled or computed range bounds to `Bytes::slice`, `Vec::slice`, or `Prng::gen_range` may silently operate on incorrect data ranges or generate random numbers from an unintended range, potentially resulting in corrupted contract state. Note that the best practice when using the `soroban-sdk` and building Soroban contracts is to always enable `overflow-checks = true`. The `stellar contract init` tool that prepares the boiler plate for a Soroban contract, as well as all examples and docs, encourage the use of configuring `overflow-checks = true` on `release` profiles so that these arithmetic operations fail rather than silently wrap. Contracts are only impacted if they use `overflow-checks = false` either explicitly or implicitly. It is anticipated the majority of contracts could not be impacted because the best practice encouraged by tooling is to enable `overflow-checks`. The fix available in `25.0.1`, `23.5.1`, and `25.0.2` replaces bare arithmetic with `checked_add` / `checked_sub`, ensuring overflow traps regardless of the `overflow-checks` profile setting. As a workaround, contract workspaces can be configured with a profile available in the GitHub Securtity Advisory to enable overflow checks on the arithmetic operations. This is the best practice when developing Soroban contracts, and the default if using the contract boilerplate generated using `stellar contract init`. Alternatively, contracts can validate range bounds before passing them to `slice` or `gen_range` to ensure the conversions cannot overflow."}, {"lang": "es", "value": "`soroban-sdk` es un SDK de Rust para contratos Soroban. El desbordamiento aritm\u00e9tico puede activarse en los m\u00e9todos `Bytes::slice`, `Vec::slice` y `Prng::gen_range` (para `u64`) en el `soroban-sdk` en versiones hasta la `25.0.1`, `23.5.1` y `25.0.2` inclusive. Los contratos que pasan l\u00edmites de rango controlados por el usuario o calculados a `Bytes::slice`, `Vec::slice` o `Prng::gen_range` pueden operar silenciosamente en rangos de datos incorrectos o generar n\u00fameros aleatorios de un rango no deseado, lo que podr\u00eda resultar en un estado de contrato corrupto. Tenga en cuenta que la mejor pr\u00e1ctica al usar el `soroban-sdk` y construir contratos Soroban es habilitar siempre `overflow-checks = true`. La herramienta `stellar contract init` que prepara el c\u00f3digo base para un contrato Soroban, as\u00ed como todos los ejemplos y la documentaci\u00f3n, fomentan el uso de configurar `overflow-checks = true` en perfiles de `release` para que estas operaciones aritm\u00e9ticas fallen en lugar de envolverse silenciosamente. Los contratos solo se ven afectados si usan `overflow-checks = false` ya sea expl\u00edcita o impl\u00edcitamente. Se anticipa que la mayor\u00eda de los contratos no se ver\u00edan afectados porque la mejor pr\u00e1ctica fomentada por las herramientas es habilitar `overflow-checks`. La correcci\u00f3n disponible en `25.0.1`, `23.5.1` y `25.0.2` reemplaza la aritm\u00e9tica b\u00e1sica con `checked_add` / `checked_sub`, asegurando que los desbordamientos se intercepten independientemente de la configuraci\u00f3n del perfil `overflow-checks`. Como soluci\u00f3n alternativa, los espacios de trabajo de contratos pueden configurarse con un perfil disponible en el Aviso de Seguridad de GitHub para habilitar las comprobaciones de desbordamiento en las operaciones aritm\u00e9ticas. Esta es la mejor pr\u00e1ctica al desarrollar contratos Soroban, y el valor predeterminado si se utiliza el c\u00f3digo base del contrato generado con `stellar contract init`. Alternativamente, los contratos pueden validar los l\u00edmites de rango antes de pasarlos a `slice` o `gen_range` para asegurar que las conversiones no puedan desbordarse."}], "lastModified": "2026-06-17T10:23:45.297", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:stellar:rs-soroban-sdk:*:*:*:*:*:rust:*:*", "vulnerable": true, "matchCriteriaId": "A32F427A-2783-4BC4-8179-FA068687C74E", "versionEndExcluding": "22.0.9"}, {"criteria": "cpe:2.3:a:stellar:rs-soroban-sdk:*:*:*:*:*:rust:*:*", "vulnerable": true, "matchCriteriaId": "007E2769-15DD-4508-90C5-B1FB89034D2D", "versionEndExcluding": "23.5.1", "versionStartIncluding": "23.0.0"}, {"criteria": "cpe:2.3:a:stellar:rs-soroban-sdk:*:*:*:*:*:rust:*:*", "vulnerable": true, "matchCriteriaId": "FE6977E5-17FB-4A06-BCF5-5ED52DFA5522", "versionEndExcluding": "25.0.2", "versionStartIncluding": "25.0.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}