github.com/open-feature/flagd/flagd
Affected
- introduced
0, fixed0.14.2(semver)
Fixed versions
0.14.2
Fix
- Fixed version
0.14.2go get github.com/open-feature/flagd/[email protected]
Advisory
Also known as: CVE-2026-31866, GO-2026-4674
flagd Vulnerable to Allocation of Resources Without Limits or Throttling
Details
flagd exposes OFREP (/ofrep/v1/evaluate/...) and gRPC (evaluation.v1, evaluation.v2) endpoints for feature flag evaluation. These endpoints are designed to be publicly accessible by client applications.
The evaluation context included in request payloads is read into memory without any size restriction. An attacker can send a single HTTP request with an arbitrarily large body, causing flagd to allocate a corresponding amount of memory. This leads to immediate memory exhaustion and process termination (e.g., OOMKill in Kubernetes environments).
flagd does not natively enforce authentication on its evaluation endpoints. While operators may deploy flagd behind an authenticating reverse proxy or similar infrastructure, the endpoints themselves impose no access control by default.
Impact
Affected Endpoints
/ofrep/v1/evaluate/flags/{flagKey} (OFREP single flag evaluation)/ofrep/v1/evaluate/flags (OFREP bulk evaluation)flagd.evaluation.v1.Service/ResolveBoolean (gRPC/Connect)flagd.evaluation.v1.Service/ResolveString (gRPC/Connect)flagd.evaluation.v1.Service/ResolveFloat (gRPC/Connect)flagd.evaluation.v1.Service/ResolveInt (gRPC/Connect)flagd.evaluation.v1.Service/ResolveObject (gRPC/Connect)flagd.evaluation.v1.Service/ResolveAll (gRPC/Connect)flagd.evaluation.v2.Service/ResolveBoolean (gRPC/Connect)flagd.evaluation.v2.Service/ResolveString (gRPC/Connect)flagd.evaluation.v2.Service/ResolveFloat (gRPC/Connect)flagd.evaluation.v2.Service/ResolveInt (gRPC/Connect)flagd.evaluation.v2.Service/ResolveObject (gRPC/Connect)High Basis: The source's own band: HIGH
0, fixed 0.14.2 (semver)0.14.2
0.14.2go get github.com/open-feature/flagd/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0