CVE-2026-55170

MEDIUMNVD 5.45.4
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 case-distinct values such as user:Alice and user:alice as equivalent, causing two distinct check requests to return the same response. This issue is fixed in 1.18.0.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

June 18, 2026

Last Modified

July 14, 2026

Advisory Details (5)

Auto-updated Jul 14, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

OpenFGA Improper Policy Enforcement · Advisory · openfga/openfga · GitHub

https://github.com/openfga/openfga/security/advisories/GHSA-cf98-j28v-49v6
github_release Patch Available

v1.18.0

Patch available: openfga/openfga v1.18.0

https://github.com/openfga/openfga/releases/tag/v1.18.0
github_commit

commit a2e0dbefc3e0 (openfga/openfga)

Fix landed in openfga/openfga commit a2e0dbefc3e0 — awaiting tagged release

https://github.com/openfga/openfga/commit/a2e0dbefc3e01a95c785f81a3563bc6571b08b11
github_release Patch Available

openfga-0.3.9

Patch available: openfga/helm-charts openfga-0.3.9

https://github.com/openfga/helm-charts/releases/tag/openfga-0.3.9
github_commit Patch Available

commit 96d5517a2693 (openfga/helm-charts)

Patch available: openfga/helm-charts openfga-0.3.9 (contains commit 96d5517a2693)

https://github.com/openfga/helm-charts/commit/96d5517a2693ff5def451dee7d6b9d1baeb281f8

Vendor Advisories for CVE-2026-55170(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/openfga/openfga1.18.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 17:42 UTCEG score recompute
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-25 14:18 UTCEPSS rescore
  4. 2026-07-24 14:18 UTCEPSS rescore
  5. 2026-07-23 14:18 UTCEPSS rescore
  6. 2026-07-23 03:20 UTCEG score recompute
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:25 UTCEPSS rescore
  9. 2026-07-20 17:08 UTCEPSS rescore
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-16 17:03 UTCEPSS rescore
  15. 2026-07-15 20:31 UTCEG score recompute 3.30
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-14 01:43 UTCNVD updateCVSS v3 → 5.4 · severity → MEDIUM
  21. 2026-07-13 22:31 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-11 08:27 UTCEPSS rescore
Show 4 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 21:42 UTCEG score recompute 2.10
  3. 2026-07-09 21:40 UTCMITRE cvelistV5CVSS v3 → 2.1 · CVSS v4 → 2.1
  4. 2026-06-18 15:07 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55170?
CVE-2026-55170 is a medium vulnerability published on June 18, 2026. 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 case-distinct values such as…
When was CVE-2026-55170 disclosed?
CVE-2026-55170 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55170 actively exploited?
CVE-2026-55170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.7% of all scored CVEs.
What is the CVSS score of CVE-2026-55170?
CVE-2026-55170 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-55170?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55170, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55170

Explore →

Is Your Infrastructure Affected by CVE-2026-55170?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.