# Ory fosite contains Improper Handling of Exceptional Conditions

Advisory record · `GHSA-7mqr-2v3q-v2wm`

- **Identifiers:** `GHSA-7mqr-2v3q-v2wm` · `CVE-2020-15223` · `GO-2021-0109`
- **State:** Confirmed
- **Severity:** CVSS 8.0 High
- **Critical:** No
- **Weakness (CWE):** [CWE-754](https://cwe.mitre.org/data/definitions/754.html) · [CWE-755](https://cwe.mitre.org/data/definitions/755.html)
- **Tags:** [CWE-754](https://agentprime.io/advisories/tag/cwe-754.md) · [CWE-755](https://agentprime.io/advisories/tag/cwe-755.md)
- **Published:** 24 May 2021
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 May 2021, 16:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/ory/fosite` (Go): affected `<0.34.0`; fixed in `0.34.0`

## Machine-written summary

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

> Ory fosite versions before 0.34.0 have a flaw in the token revocation handler, which ignores errors returned by storage. When storage fails, the handler can still return a success status even though the token remains valid. Exploitation depends on an attacker being able to trigger storage errors. Upgrade to fosite 0.34.0 or later.

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

- 8.0 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 14:46 UTC: First seen by agentprime
- 31 Oct 2026, 14:46 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7mqr-2v3q-v2wm)

## Sources

- [GitHub Advisory Database: GHSA-7mqr-2v3q-v2wm](https://github.com/advisories/GHSA-7mqr-2v3q-v2wm)
- [OSV: GHSA-7mqr-2v3q-v2wm](https://osv.dev/vulnerability/GHSA-7mqr-2v3q-v2wm)
- <https://github.com/ory/fosite/security/advisories/GHSA-7mqr-2v3q-v2wm>
- <https://nvd.nist.gov/vuln/detail/CVE-2020-15223>
- <https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319>
- <https://pkg.go.dev/vuln/GO-2021-0109>
- <https://tools.ietf.org/html/rfc7009#section-2.2.1>

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-7mqr-2v3q-v2wm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7mqr-2v3q-v2wm/>. Everything for agents: <https://agentprime.io/llms.txt>.