Authorization bypass via case-insensitive identifier comparison
Published Jul 9, 2026 · Updated Jul 9, 2026
Improper policy enforcement in OpenFGA before 1.18.0 allows remote authenticated users to receive incorrect authorization decisions. The MySQL schema applies case-insensitive collation to identifier columns in tuple, changelog, and authorization_model, so values such as user:Alice and user:alice compare as the same identity. Exploitation requires MySQL storage and authorization rules that treat user strings as case-sensitive, enabling access granted to the case-distinct identity.
Summary
What happened
Improper policy enforcement in OpenFGA before 1.18.0 allows remote authenticated users to receive incorrect authorization decisions. The MySQL schema applies case-insensitive collation to identifier columns in tuple, changelog, and authorization_model, so values such as user:Alice and user:alice compare as the same identity. Exploitation requires MySQL storage and authorization rules that treat user strings as case-sensitive, enabling access granted to the case-distinct identity.
The record
- CVE
- CVE-2026-55170
- Published
- Jul 9, 2026
- Updated
- Jul 9, 2026
- Vendor
- OpenFGA
- Product
- OpenFGA
- Classifications
- CWE-178, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2026CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.18.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo