Ory fosite contains Improper Handling of Exceptional Conditions (CVE-2020-15223) | HOL Guard CVE

High · CVSS 8.0CVE-2020-15223GHSA-7MQR-2V3Q-V2WM

Ory fosite contains Improper Handling of Exceptional Conditions

Answer in brief

CVE-2020-15223 records a High severity (CVSS 8.0) vulnerability in Ory fosite contains Improper Handling of Exceptional Conditions. The current sources do not mark it as known exploited. The current feed maps github.com/ory/fosite (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published May 24, 2021Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Aug 7, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.0
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 8.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps github.com/ory/fosite (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
github.com/ory/fositego	>=0 <0.34.0	0.34.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for github.com/ory/fosite.
Review the reported fix. Update github.com/ory/fosite to 0.34.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
May 24, 2021
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Aug 7, 2026

Sources and claim methodology

Upstream source description

### Impact The `TokenRevocationHandler` ignores errors coming from the storage. This can lead to unexpected 200 status codes indicating successful revocation while the token is still valid. Whether an attacker can use this for her advantage depends on the ability to trigger errors in the store. ### References [RFC 7009](https://tools.ietf.org/html/rfc7009#section-2.2.1) states that a 503 HTTP code must be returned when the server has a problem.

Quoted source text, attributed separately from HOL analysis.