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.
CVE-2026-45137
This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EPSS
- 15.7%
- KEV
- Not listed
Published
May 13, 2026
Last Modified
May 29, 2026
Advisory Details (1)
Auto-updated Jun 3, 2026Program<'info, System> is not properly validated · Advisory · otter-sec/anchor · GitHub
https://github.com/otter-sec/anchor/security/advisories/GHSA-c6rc-8jpp-2fgcVendor Advisories for CVE-2026-45137(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
crates.io(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| anchor-lang | — | 1.0.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 53× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 12:54 UTCEG score recompute
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 23:46 UTCEG score recompute
- 2026-06-27 09:31 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 20:34 UTCEG score recompute
- 2026-06-25 19:55 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
Show 66 moreShow fewer
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:25 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 14:42 UTCEG score recompute
- 2026-06-16 22:46 UTCEG score recompute
- 2026-06-16 17:52 UTCEPSS rescore
- 2026-06-16 03:09 UTCEG score recompute
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 01:46 UTCEG score recompute
- 2026-06-14 12:50 UTCEG score recompute
- 2026-06-13 23:50 UTCEG score recompute
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 04:53 UTCEG score recompute
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 14:52 UTCEG score recompute
- 2026-06-12 01:55 UTCEG score recompute
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-11 12:59 UTCEG score recompute
- 2026-06-11 00:01 UTCEG score recompute
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 11:04 UTCEG score recompute
- 2026-06-09 22:08 UTCEG score recompute
- 2026-06-09 09:03 UTCEG score recompute
- 2026-06-08 20:03 UTCEG score recompute
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 14:17 UTCEPSS rescore
- 2026-06-08 06:24 UTCEG score recompute
- 2026-06-07 17:28 UTCEG score recompute
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 15:25 UTCEPSS rescore
- 2026-06-07 04:31 UTCEG score recompute
- 2026-06-06 15:35 UTCEG score recompute
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 13:47 UTCEPSS rescore
- 2026-06-06 02:38 UTCEG score recompute
- 2026-06-05 22:47 UTCEPSS rescore
- 2026-06-05 13:42 UTCEG score recompute
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 06:10 UTCEPSS rescore
- 2026-06-05 00:46 UTCEG score recompute
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 13:12 UTCEPSS rescore
- 2026-06-04 11:50 UTCEG score recompute
- 2026-06-03 22:54 UTCEG score recompute
- 2026-06-03 09:57 UTCEG score recompute
- 2026-06-02 21:01 UTCEG score recompute
- 2026-06-02 20:13 UTCEPSS rescore
- 2026-06-02 08:04 UTCEG score recompute
- 2026-06-01 19:07 UTCEG score recompute
- 2026-06-01 13:52 UTCEPSS rescore
- 2026-06-01 13:52 UTCEPSS rescore
- 2026-06-01 06:11 UTCEG score recompute
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-31 00:16 UTCEPSS rescore
- 2026-05-29 13:44 UTCEPSS rescore
- 2026-05-29 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-24 06:19 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2002-2444EG 9.8CRITICAL
- CVE-2005-0116NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2002-1359NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2000-0380NVD 0.0EG 9.0EPSS 98%NONE
- CVE-2000-0258EG 7.5EPSS 97%HIGH
- CVE-2004-2771EG 0.0EPSS 93%NONE
- CVE-2002-2443EG 0.0EPSS 93%NONE
- CVE-2002-2433EG 0.0NONE
- CVE-2003-1569EG 0.0NONE
- CVE-2003-1568EG 0.0NONE
Frequently asked(5)
What is CVE-2026-45137?
When was CVE-2026-45137 disclosed?
Is CVE-2026-45137 actively exploited?
What is the CVSS score of CVE-2026-45137?
How do I remediate CVE-2026-45137?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45137
Is Your Infrastructure Affected by CVE-2026-45137?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.