Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
stellar-strkey versions before 0.0.8 can panic when SignedPayload::from_payload is given a specially crafted payload whose embedded length field is 0xffffffff, which causes an arithmetic overflow. The source does not say what an attacker can do beyond triggering the panic, or what kind of access is required. Upgrade to stellar-strkey 0.0.8. Alternatively, reject payloads whose 4-byte length field at offset 32 decodes to a value above 64 before passing them to the function.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0095, the 61st percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:17 UTC First seen by agentprime
- 31 Oct 2026, 15:17 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-5873-6fwq-463f
- OSV: GHSA-5873-6fwq-463f
- github.com/stellar/rs-stellar-strkey/security/advisories/GHSA-5873-6fwq-463f
- nvd.nist.gov/vuln/detail/CVE-2023-46135
- github.com/stellar/rs-stellar-strkey/issues/58
- github.com/stellar/rs-stellar-strkey/pull/59
- github.com/stellar/rs-stellar-strkey/commit/83adad0f5b1cda693c7ba8524d395add8077865f
- github.com/stellar/rs-stellar-strkey
- github.com/stellar/rs-stellar-strkey/releases/tag/v0.0.8