RATATOSK
← All releases

OpenFeatureflagd/v0.19.0

Security 2Breaking changes 1

Get OpenFeature alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Security2high1

flagd JSON Logic context injection fixed

high
Affectsthe flagd binary, Go core, and Go in-process provider

In targeting rules where an if branch returns a context value, or filter, some, all or none uses an outer context value, a crafted evaluation request could expose context data or crash the process. The update uses jsonlogic v3.10.2, which fixes the issue.

GHSA-2wfx-5gcf-mprwGHSA-mw4w-7w23-cg45
Show release-note lines
* **security:** bump jsonlogic to v3.10.2 (GHSA-mw4w-7w23-cg45) ([#2129](https://github.com/open-feature/flagd/issues/2129)) ([bf85e04](https://github.com/open-feature/flagd/commit/bf85e04d95c1b850a28fe883cde767db969cf37d))
github.com/open-feature/flagd/releases/tag/flagd/v0.19.0
Security advisory
flagd affected by jsonlogic context injection (GHSA-mw4w-7w23-cg45)
github.com/open-feature/flagd/security/advisories/GHSA-2wfx-5gcf-mprw

go-jose JWK parsing CPU-exhaustion issue fixed

Affectsapplications using github.com/go-jose/go-jose/v4 to parse JWKs
Additional actionNo additional setting is needed for the default 4096-bit limit; MaxRSAModulusBits must be set before parsing to allow a higher limit.

A crafted RSA key in a JWK could make parsing consume excessive CPU. Parsing now rejects RSA moduli over 4096 bits by default; the limit can be raised by setting MaxRSAModulusBits before parsing.

Show release-note lines
* **security:** update module github.com/go-jose/go-jose/v4 to v4.1.6 [security] ([#2114](https://github.com/open-feature/flagd/issues/2114)) ([bf167aa](https://github.com/open-feature/flagd/commit/bf167aaa7686f78bcd206f8b76365d4babfb5a5d))
github.com/open-feature/flagd/releases/tag/flagd/v0.19.0

Breaking changes1

Invalid flagd port values now terminate startup

Affectsservice, management, OFREP, or sync ports configured through flags or environment variables, including FLAGD_PORT

Previously, a non-numeric value such as FLAGD_PORT=abc could be converted to 0, causing flagd to bind to an ephemeral OS port. Now, invalid values—including non-numeric values and numbers outside the uint16 range of 0 to 65535—cause flagd to terminate at startup.

Evidence“Implemented `getPort(flagName string) (uint16, error)` in `flagd/cmd/start.go` using `cast.ToUint16E` and bounds checking against `math.MaxUint16` to parse values from environment/flags, verifying that values are numeric and strictly within valid TCP port range `[0, 65535]`.” open-feature/flagd/pull/2107 ↗
Show release-note lines
* **cmd:** validate port is numeric and valid uint16 ([#2107](https://github.com/open-feature/flagd/issues/2107))
* **cmd:** validate port is numeric and valid uint16 ([#2107](https://github.com/open-feature/flagd/issues/2107)) ([3fa8064](https://github.com/open-feature/flagd/commit/3fa8064e2105b7e41f360f74695e8dbcca5c9513))
github.com/open-feature/flagd/releases/tag/flagd/v0.19.0

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.