# songquanpeng one-api has an issue that results in business logic errors

Advisory record · `GHSA-7v3v-cp44-vc8m`

- **Identifiers:** `GHSA-7v3v-cp44-vc8m` · `CVE-2026-11465` · `GO-2026-6126`
- **State:** Confirmed
- **Severity:** CVSS 2.3 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-840](https://cwe.mitre.org/data/definitions/840.html)
- **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) · [CWE-840](https://agentprime.io/advisories/tag/cwe-840.md)
- **Published:** 8 Jun 2026
- **Updated:** 18 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Jun 2026, 00:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/songquanpeng/one-api` (Go): affected `>=0.1.6-alpha, <=0.6.11-preview.7`; no fixed version yet

## Machine-written summary

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

> Records: package github.com/songquanpeng/one-api, versions from 0.1.6-alpha through 0.6.11-preview.7. The source describes a flaw in the Redeem function of the redemption code top-up endpoint that leads to business logic errors. A remote attacker could trigger this, but the source says it is difficult to exploit, and a public exploit exists. No fixed version is listed, so no fix is available yet.

Written 6 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

- 2.3 Low, CVSS 4.0: `CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`, from CNA (VulDB)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0022, the 12th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:50 UTC: First seen by agentprime
- 31 Oct 2026, 14:50 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7v3v-cp44-vc8m)

## Sources

- [GitHub Advisory Database: GHSA-7v3v-cp44-vc8m](https://github.com/advisories/GHSA-7v3v-cp44-vc8m)
- [OSV: GHSA-7v3v-cp44-vc8m](https://osv.dev/vulnerability/GHSA-7v3v-cp44-vc8m)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-11465>
- <https://github.com/songquanpeng/one-api/issues/2397>
- <https://github.com/songquanpeng/one-api/pull/2399>
- <https://github.com/songquanpeng/one-api>
- <https://vuldb.com/cve/CVE-2026-11465>
- <https://vuldb.com/submit/833320>
- <https://vuldb.com/vuln/369085>
- <https://vuldb.com/vuln/369085/cti>

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-7v3v-cp44-vc8m>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7v3v-cp44-vc8m/>. Everything for agents: <https://agentprime.io/llms.txt>.