# kora-lib: Unrecognized Instruction Types Create Empty Stubs That Bypass Fee Payer Policy

Advisory record · `GHSA-x442-m7cc-hr92`

- **Identifiers:** `GHSA-x442-m7cc-hr92`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-693](https://cwe.mitre.org/data/definitions/693.html)
- **Tags:** [CWE-693](https://agentprime.io/advisories/tag/cwe-693.md)
- **Published:** 12 Mar 2026
- **Updated:** 14 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 12 Mar 2026, 14:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `kora-lib` (crates.io): affected `<2.0.5`; fixed in `2.0.5`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Kora-lib versions before 2.0.5 are affected. When inner CPI instructions use types the parser does not recognize, such as certain Token-2022 extension instructions, they are rebuilt as empty stubs that fail deserialization and are silently skipped by fee payer policy checks. An attacker who can submit transactions that include such inner instructions could use the fee payer in those instructions without the policy being enforced, though the source notes this requires the fee payer to hold an authority role on Token-2022 accounts. Upgrade to kora-lib 2.0.5 or later.

Written 8 Nov 2026.

## 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 not published, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 15:19 UTC: First seen by agentprime
- 31 Oct 2026, 15:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x442-m7cc-hr92)

## Sources

- [GitHub Advisory Database: GHSA-x442-m7cc-hr92](https://github.com/advisories/GHSA-x442-m7cc-hr92)
- [OSV: GHSA-x442-m7cc-hr92](https://osv.dev/vulnerability/GHSA-x442-m7cc-hr92)
- <https://github.com/solana-foundation/kora/security/advisories/GHSA-x442-m7cc-hr92>
- <https://github.com/solana-foundation/kora>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x442-m7cc-hr92>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x442-m7cc-hr92/>. Everything for agents: <https://agentprime.io/llms.txt>.