Skip to content

GHSA-68m9-983m-f3v5 CVE-2026-40293 GO-2026-5170

OpenFGA: Unauthenticated playground endpoint discloses preshared API key in HTML response

Medium Go
Severity
6.5 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.29%
Chance of exploitation in the next 30 days. Higher than 21.23% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
1.14.0
Upgrade github.com/openfga/openfga to this version or later

Description

Description

When OpenFGA is configured to use preshared-key authentication with the built-in playground enabled, the local server includes the preshared API key in the HTML response of the /playground endpoint. The /playground endpoint is enabled by default and does not require authentication. It is intended for local development and debugging and is not designed to be exposed to production environments.

Am I Affected?

You are affected if you meet each of the following preconditions:

  • You are running OpenFGA with --authn-method preshared, and
  • The playground is enabled, and
  • The playground endpoint is accessible beyond localhost or trusted networks.

Fix

Upgrade to OpenFGA v1.14.0, or disable the playground by running ./openfga run --playground-enabled=false.

Affected versions

Go

PackageVulnerableFixed in
github.com/openfga/openfga
>= 0.1.4, < 1.14.0
1.14.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/openfga/openfga Go → 1.14.0

go
go get github.com/openfga/openfga@v1.14.0 && go mod tidy

Severity breakdown

CVSS 3.1 6.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-g3pg-frfm-pr2m
OpenFGA: ListUsers returns a deliberately-excluded user when a `but not` exclusion under a type-bound wildcard is intersected (`and`) with another relation that also grants that user
Medium Also affects github.com/openfga/openfga
GHSA-hcxc-wf8j-23hv
OpenFGA: OIDC audience validation skipped when --authn-oidc-audience is unset
High Also affects github.com/openfga/openfga
GHSA-cf98-j28v-49v6
OpenFGA Improper Policy Enforcement
Medium Also affects github.com/openfga/openfga
GHSA-8396-jffm-qx4w
OpenFGA has cache-key delimiter injection in shared-iterator and v2 iterator that caches enables intra-store authorization-decision poisoning
Medium Also affects github.com/openfga/openfga
GHSA-57j5-qwp2-vqp6
OpenFGA has Improper Policy Enforcement
Medium Also affects github.com/openfga/openfga
GHSA-jwvj-g8pc-cx45
OpenFGA's BatchCheck within-request deduplication produces incorrect authorization decisions via list-value cache-key collision
High Also affects github.com/openfga/openfga
GHSA-h6c8-cww8-35hf
OpenFGA has an Authorization Bypass through cached keys
Critical Also affects github.com/openfga/openfga
GHSA-jq9f-gm9w-rwm9
OpenFGA Improper Policy Enforcement
High Also affects github.com/openfga/openfga
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor