Is CVE-2026-48096 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-48096 being exploited in the wild.

How severe is CVE-2026-48096?

Medium severity, with a CVSS score of 5, published 10 June 2026.

Which products and versions are affected?

github.com/openfga/openfga (Go) < 1.16.0, SEMVER:introduced=0,fixed=1.16.0; OpenFGA < 1.16.0, <= v1.15.1.

Is there a fix for CVE-2026-48096?

Yes. github.com/openfga/openfga (Go): upgrade to 1.16.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-48096 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-48096?

Check whether you run github.com/openfga/openfga (Go) or OpenFGA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-48096: OpenFGA cache key collision in iterator caching

Q: Is there a fix for CVE-2026-48096?

Yes. github.com/openfga/openfga (Go): upgrade to 1.16.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-48096 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-48096?

Check whether you run github.com/openfga/openfga (Go) or OpenFGA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-48096 · Severity: medium · CVSS 5 · Published 2026-06-10

OpenFGA, an open-source authorization engine, is vulnerable to a caching issue that could lead to incorrect access control decisions. When specific caching features are enabled, the system may confuse two different authorization requests and return a previously stored result for the wrong user or resource. This could allow unauthorized access to data or prevent legitimate users from performing actions.

Technologies: github.com/openfga/openfga (Go), OpenFGA. Vendors: Go, OpenFGA.

Quick answers

Is CVE-2026-48096 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-48096 being exploited in the wild.
How severe is CVE-2026-48096?: Medium severity, with a CVSS score of 5, published 10 June 2026.
Which products and versions are affected?: github.com/openfga/openfga (Go) < 1.16.0, SEMVER:introduced=0,fixed=1.16.0; OpenFGA < 1.16.0, <= v1.15.1.
Is there a fix for CVE-2026-48096?: Yes. github.com/openfga/openfga (Go): upgrade to 1.16.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-48096 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-48096?: Check whether you run github.com/openfga/openfga (Go) or OpenFGA at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/openfga/openfga (Go): upgrade to 1.16.0 or later
```
go get github.com/openfga/openfga@v1.16.0
```

Technical details

OpenFGA contains a cache-key delimiter injection vulnerability in its shared-iterator and v2 iterator components. When iterator caching is enabled (specifically SharedIteratorCache and ListObjectsIteratorCache), the system fails to properly distinguish between distinct check requests during key generation. This allows two different requests to produce the same cache key, leading to intra-store authorization-decision poisoning where a cached result from one request is incorrectly served for another. Attackers with low privileges can potentially exploit this over the network, though the attack complexity is high. The issue is addressed in version 1.16.0.

Affected products

OpenFGA OpenFGA < 1.16.0

Identifiers

CVE-2026-48096
GHSA-8396-jffm-qx4w
GO-2026-5239

Timeline

2026-06-05: disclosed
2026-06-10: advisory: NVD publication
2026-06-11: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.