FlawAtlas
Search the atlas
CVE-2026-31866 High

flagd Vulnerable to Allocation of Resources Without Limits or Throttling in github.com/open-feature/flagd/flagd

flagd Vulnerable to Allocation of Resources Without Limits or Throttling in github.com/open-feature/flagd/flagd

Exploit probability 0.4%
Published March 12, 2026
Required by Not available
Last source change March 23, 2026

02 / AFFECTED SOFTWARE

Affected packages

Unknown Unknown

187 explicit affected versions

Go github.com/open-feature/flagd/flagd
Go github.com/open-feature/flagd/flagd

03 / CONNECTIONS

Connected vulnerabilities

related OPENSUSE-SU-2026:21483-1

04 / EVIDENCE

Source records

Open Source Vulnerabilities GHSA-rmrf-g9r3-73pm

## 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 - **Denial of Service:** A single crafted request can crash the flagd process. - **Service Disruption:** All applications relying on the affected flagd instance for feature flag evaluation will lose access to flag evaluations until the process restarts. - **Repeated Exploitation:** An attacker can continuously send oversized requests to prevent recovery. ## 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)

View original source
Open Source Vulnerabilities GO-2026-4674

flagd Vulnerable to Allocation of Resources Without Limits or Throttling in github.com/open-feature/flagd/flagd

View original source
Open Source Vulnerabilities CVE-2026-31866

flagd is a feature flag daemon with a Unix philosophy. Prior to 0.14.2, 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. This vulnerability is fixed in 0.14.2.

View original source

05 / REFERENCES

Further evidence