LiveActive security incident?Get immediate response
CVE Record

CVE-2026-40293: OpenFGA Playground Preshared Key Exposure

OpenFGA is an authorization/permission engine built for developers. In versions 0.1.4 through 1.13.1, 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. Only those who run OpenFGA with `--authn-method` preshared, with the playground enabled, and with the playground endpoint accessible beyond localhost or trusted networks are vulnerable. To remediate the issue, users should upgrade to OpenFGA v1.14.0, or disable the playground by running `./openfga run --playground-enabled=false.`

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

OpenFGA can reveal its preshared API key inside the publicly accessible playground page. An unauthenticated visitor who can reach that page may obtain the secret used to authenticate API requests. Production systems are at risk only when preshared-key authentication, the enabled playground, and exposure beyond localhost or trusted networks occur together.

Executive priority

High priority for production deployments meeting all exposure conditions; remediate promptly because an unauthenticated network visitor could obtain an authentication secret. Lower the priority only after confirming the playground is disabled, inaccessible from untrusted networks, or preshared-key authentication is not used.

Technical view

OpenFGA versions 0.1.4 through 1.13.1 embed the configured preshared key in the HTML response from the unauthenticated /playground endpoint. Exploitation requires network access to that endpoint, preshared-key authentication, and the playground being enabled. The issue is classified as CWE-200 and CWE-201, with CVSS 3.1 score 7.5 for high confidentiality impact.

Likely exposure

Exposure is configuration-dependent. Prioritize internet-facing or broadly reachable OpenFGA deployments below version 1.14.0. Deployments using another authentication method, disabling the playground, or limiting it to localhost or trusted networks do not meet the stated vulnerable conditions.

Exploitation context

The disclosure requires no authentication, user interaction, or complex prerequisite beyond reaching the playground. The bundle reports no CISA KEV listing and provides no evidence of active exploitation. Treat accessible production instances urgently because the disclosed value is an authentication secret.

Researcher notes

The vulnerable behavior is secret inclusion in server-generated playground HTML, not a general OpenFGA authentication bypass. Scope validation should combine version, authentication mode, playground state, and network reachability. The supplied evidence supports confidentiality impact but does not establish secret use, downstream compromise, or exploitation in the wild.

Mitigation direction

  • Upgrade OpenFGA to version 1.14.0 or later.
  • Alternatively, start OpenFGA with the playground disabled.
  • Restrict the playground endpoint to localhost or trusted networks while remediation is pending.
  • Review current OpenFGA vendor guidance before applying environment-specific changes.

Validation and detection

  • Inventory OpenFGA versions and identify deployments older than 1.14.0.
  • Confirm whether each deployment uses preshared-key authentication.
  • Confirm whether the built-in playground is enabled.
  • Test whether /playground is reachable from untrusted networks without authentication.
  • After remediation, verify the playground response no longer exposes the preshared key.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-201: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-40293 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6redhat-SADP
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-40293Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPOpenFGA: github.com/openfga/openfga: OpenFGA: Information disclosure of preshared API key via playground endpoint
other:Red Hat severity ratingcvssV3_1
  • 2026-04-17T22:01:37.276Z: Reported to Red Hat.
  • 2026-04-17T20:47:06.804Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
openfgaopenfga>= 0.1.4, < 1.14.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-201 · source CWE mapping

Insertion of Sensitive Information Into Sent Data

Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.