Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

OpenFGA has an Authorization Bypass through cached keys

CVSS 4.0 5.8 MEDIUMEUVD CVSS 4.0 5.8 CVSS 4.0 · [email protected] · Secondary 5.8 MEDIUMCVSS 3.1 · [email protected] · Primary 9.8 CRITICALCVSS_V4 Publisher rating MODERATEFixed by github.com/openfga/openfga 1.13.1osv · severity unknownFixed by github.com/openfga/openfga 1.13.1KEV status unknown

cve-program · CVE-2026-33729

Published

OpenFGA is a high-performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar. In versions prior to 1.13.1, under specific conditions, models using conditions with caching enabled can result in two different check requests producing the same cache key. This can result in OpenFGA reusing an earlier cached result for a different request. Users are affected if the model has relations which rely on condition evaluation andncaching is enabled. OpenFGA v1.13.1 contains a patch.

Read the publisher's advisory

euvd · EUVD-2026-16507

Published

OpenFGA is a high-performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar. In versions prior to 1.13.1, under specific conditions, models using conditions with caching enabled can result in two different check requests producing the same cache key. This can result in OpenFGA reusing an earlier cached result for a different request. Users are affected if the model has relations which rely on condition evaluation andncaching is enabled. OpenFGA v1.13.1 contains a patch.

Read the publisher's advisory

nvd · CVE-2026-33729

Published

OpenFGA is a high-performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar. In versions prior to 1.13.1, under specific conditions, models using conditions with caching enabled can result in two different check requests producing the same cache key. This can result in OpenFGA reusing an earlier cached result for a different request. Users are affected if the model has relations which rely on condition evaluation andncaching is enabled. OpenFGA v1.13.1 contains a patch.

Read the publisher's advisory

osv · GHSA-h6c8-cww8-35hf

Published

### Description In OpenFGA, under specific conditions, models using conditions with caching enabled can result in two different check requests producing the same cache key. This can result in OpenFGA reusing an earlier cached result for a different request. ### Am I Affected? Users are affected if the following preconditions are met: 1. The model has relations which rely on condition evaluation. 1. Caching is enabled. ### Fix Upgrade to OpenFGA v1.13.1. ### Acknowledgement OpenFGA would like to thank @Amemoyoi for the discovery and responsible disclosure.

Read the publisher's advisory

osv · GO-2026-4857

Published

OpenFGA has an Authorization Bypass through cached keys in github.com/openfga/openfga

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-33729

Published

openfga

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "openfga",
                    "product": "openfga",
                    "versions": [
                        {
                            "version": "< 1.13.1",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-16507

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Mar 27, 2026, 12:27:40 AM

dateUpdated: Mar 30, 2026, 11:53:10 AM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-33729

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-20 · CWE-345 · CWE-1289

Original publisher date fields

published: 2026-03-27T01:16:20.367

lastModified: 2026-06-17T10:38:00.100

1 source CPE criteria · context only
  • cpe:2.3:a:openfga:openfga:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-h6c8-cww8-35hf

Published

github.com/openfga/openfga

Go

SEMVER · introduced 0 → fixed 1.13.1

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2026-4857

Published

github.com/openfga/openfga

Go

SEMVER · introduced 0 → fixed 1.13.1

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 15 Nov 12:11 UTC · 256 of 275 readable · 252 fully read · documentation 469/469 current