Vulnerability in anchor-lang (CVE-2026-45137)
Summary
Vulnerability in anchor-lang (CVE-2026-45137). Data can be tampered with by attackers. Mitigation: upgrade to 1.0.2 or later.
Original description
The description as published by the source.
Anchor is a framework providing several convenient developer tools for writing Solana programs. From 1.0.0 to before 1.0.2, an logic error causes anchor programs to accept any program id when requiring the system program id, causing false assumptions resulting in potential arbitrary cpi in programs that invoke system program instructions. In the TryFrom<&'a AccountInfo<'a>> implementation for Program<'a, T>, the id of T is compared with Pubkey::default() to check whether anchor should allow any executable account, or a specific account, because when no T is supplied, T defaults to (), which implements Id::id() by returning Pubkey::default(). This results in T = () and T = System (which has Pubkey::default() as the id) having the same behavior, both allow any executable account. Programs built with anchor assume that the anchor runtime verifies passed in programs of type Program<'a, System> are in fact the system program. This false assumption can lead to arbitrary CPI or payment bypassing when programs try making CPI calls to the system program using the passed in system program due to the fact that the attacker can pass in any program instead of the system program. This vulnerability is fixed in 1.0.2.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45137 has been found in anchor-lang.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: upgrade anchor-lang to 1.0.2 or later.
If unsure, ask your IT team or search "anchor-lang CVE-2026-45137" on the vendor's site.
CVE-2026-45137 (anchor-lang) — CWE-20 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.0.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in anchor-lang.
Check the vendor advisory for the affected versions of anchor-lang.
Severity: High (CVSS 8.2/10). Data can be tampered with by attackers.
Update to 1.0.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'anchor-lang' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'anchor-lang' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
anchor-langを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade anchor-lang to 1.0.2ステージング環境で 1.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory rustsec.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package crates.io
- web github.com
- web github.com
- web github.com
- web github.com