# CVE-2025-22866: Timing sidechannel for P-256 on ppc64le in crypto/internal/nistec > Timing side-channel in Go's P-256 implementation on ppc64le leaks secret scalar bits, potentially exposing partial private key information. - **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Feb 2025 - **Updated:** 21 Feb 2025 - **Also known as:** BIT-golang-2025-22866, CLEANSTART-2026-JE88659, CLEANSTART-2026-PR48367, DEBIAN-CVE-2025-22866, ECHO-2ad3-2ee4-a992, GHSA-3whm-j4xm-rv8x, GO-2025-3447, MGASA-2025-0065, MINI-2qgc-4fwc-8r9q, MINI-3gv2-jgcj-2895, MINI-44pr-wwvj-3gh7, MINI-5w58-7r87-cqcc, MINI-6p6j-prf2-mmpw, MINI-73j4-jjh5-fv8h, MINI-7q43-2h4q-7q59, MINI-87h2-rp59-gwr7, MINI-8qh8-jhq2-fc4v, MINI-c63c-82gc-hhpc, MINI-fhh9-ffp3-m575, MINI-hg5v-4wqc-7m67, MINI-j2gp-vmm9-g8r3, MINI-jc38-jxqg-2gc3, MINI-pggv-5j2f-v8jf, MINI-v6wv-2pxm-97pq, MINI-v7hv-hgvp-3w4w, MINI-vm6q-4grm-6hjc, MINI-vwxw-wcjc-8jwf, MINI-w887-c9h5-mh62, MINI-x2g7-37cp-6m4m, ROOT-OS-DEBIAN-12-CVE-2025-22866, SUSE-SU-2025:0392-1, SUSE-SU-2025:0393-1, UBUNTU-CVE-2025-22866, openSUSE-SU-2025:14745-1, openSUSE-SU-2025:14746-1 ## What is CVE-2025-22866? CVE-2025-22866 is a medium-severity vulnerability in Go standard library crypto/internal/nistec, published on 6 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Due to the usage of a variable time instruction in the assembly implementation of an internal function, a small number of bits of secret scalars are leaked on the ppc64le architecture. Due to the way this function is used, we do not believe this leakage is enough to allow recovery of the private key when P-256 is used in any well known protocols. ## Which versions are affected by CVE-2025-22866? 2 open source packages ship an affected version, including golang and stdlib. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `golang` | Bitnami | All versions | 1.22.12, 1.23.6, 1.24.0 | | `stdlib` | Go | All versions | 1.22.12, 1.23.6, 1.24.0-rc.3 | | `go1.22` | SUSE:Linux Enterprise Module for Development Tools 15 SP6 | All versions | 1.22.12-150000.1.42.1 | | `go1.23` | SUSE:Linux Enterprise Module for Development Tools 15 SP6 | All versions | 1.23.6-150000.1.21.1 | | `go1.22` | openSUSE:Leap 15.6 | All versions | 1.22.12-150000.1.42.1 | | `go1.23` | openSUSE:Leap 15.6 | All versions | 1.23.6-150000.1.21.1 | | `go1.22` | openSUSE:Tumbleweed | All versions | 1.22.12-1.1 | | `go1.23` | openSUSE:Tumbleweed | All versions | 1.23.6-1.1 | ## How do I fix CVE-2025-22866? Upgrade golang to a fixed version for your release line: 1.22.12, 1.23.6 or 1.24.0. ## Is CVE-2025-22866 being exploited? There is no known exploitation of CVE-2025-22866 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-22866 and fix it if it is affected. What it is: CVE-2025-22866 is a medium-severity vulnerability in Go standard library crypto/internal/nistec, published on 6 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-22866 in the wild and no public exploit code. Affected packages and fixed versions: - golang (Bitnami): affected all versions; fixed in 1.22.12, 1.23.6, 1.24.0 - stdlib (Go): affected all versions; fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-22866/ (Markdown: https://insights.sbomify.com/CVE-2025-22866/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22866 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22866 - OSV: https://osv.dev/vulnerability/CVE-2025-22866 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-22866/ Summaries are generated and may contain mistakes; the official description above is the record.