CVE-2026-55170 in OpenFGA Helm Charts
OpenFGA is an authorization/permission engine built for developers. Prior to 1.18.0, when MySQL is being used as the datastore and authorization decisions rely on case-sensitive user strings, the tuple, changelog, and authorization_model identifier columns can compare...
Quick answer
OpenFGA Helm Charts should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- OpenFGA before 1.18.0 when using MySQL datastore
Fixed versions
- OpenFGA 1.18.0 or OpenFGA Helm chart openfga-0.3.9
How to fix it
Update OpenFGA Helm Charts. The old OpenFGA setup can accept the wrong token or compare users in an unsafe way.
- Upgrade openfga/helm-charts and OpenFGA to OpenFGA 1.18.0 or OpenFGA Helm chart openfga-0.3.9.
- Review OIDC audience settings.
- Apply Helm chart changes in staging first.
- Redeploy and check authorization results.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the OpenFGA version and Helm chart are fixed.
- Scan again and confirm CVE-2026-55170 is gone.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-55170?
OpenFGA Helm Charts versions listed as affected should be reviewed: OpenFGA before 1.18.0 when using MySQL datastore.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.