critical CVSS 9.8

CVE-2024-56323·Docker vulnerability

OpenFGA is an authorization/permission engine. IN OpenFGA v1.3.8 to v1.8.2 (Helm chart openfga-0.1.38 to openfga-0.2.19, docker v1.3.8 to v.1.8.2) are vulnerable to authorization bypass under the following conditions: 1. calling Check API or ListObjects with a model that uses [conditions](https://openfga.dev/docs/modeling/conditions), and 2. calling Check API or ListObjects API with [contextual tuples](https://openfga.dev/docs/concepts#what-are-contextual-tuples) that include conditions and 3. OpenFGA is configured with caching enabled (`OPENFGA_CHECK_QUERY_CACHE_ENABLED`). Users are advised to upgrade to v1.8.3. There are no known workarounds for this vulnerability.

Severity
critical
Software
Docker
Fixed in
1.8.3
Published
2025-01-13

Affected versions

From: 1.3.8

Until: 1.8.3

Fixed in: 1.8.3

How to fix this CVE

OpenFGA versions 1.3.8 through 1.8.2 contain a critical authorization bypass flaw when using conditional models with contextual tuples and query caching enabled. Immediately upgrade Docker and OpenFGA to version 1.8.3 or later to patch this vulnerability. Review your authorization policies for any unauthorized access that may have occurred while running vulnerable versions.

sudo dnf update docker-ce docker-ce-cli

Defensia detects this vulnerability

How to check if you are affected

  1. Check installed OpenFGA version: docker ps --filter ancestor=openfga/openfga --format '{{.Image}}' and verify the tag is 1.8.3 or higher
  2. Verify Docker version: docker --version and confirm it is up-to-date with latest stable release
  3. Check if OPENFGA_CHECK_QUERY_CACHE_ENABLED is set to true: docker inspect <container-id> | grep -i cache
  4. Review authorization audit logs for unexpected Check API or ListObjects calls with contextual tuples between vulnerability discovery and patch date
  5. Confirm patch application: curl http://localhost:8080/healthz (or appropriate endpoint) and verify version header shows v1.8.3+

FAQ

What is CVE-2024-56323?

CVE-2024-56323 is a critical authorization bypass vulnerability in OpenFGA that occurs when conditional models are used with contextual tuples and query caching is enabled. This allows attackers to bypass permission checks and gain unauthorized access to protected resources.

Is CVE-2024-56323 being actively exploited?

No, CVE-2024-56323 is not currently listed in the CISA KEV catalog and no public exploits have been released, but the critical CVSS score of 9.8 demands immediate patching.

What versions of Docker/OpenFGA are affected by CVE-2024-56323?

OpenFGA versions 1.3.8 through 1.8.2 (Docker images v1.3.8 to v1.8.2, Helm chart versions openfga-0.1.38 to openfga-0.2.19) are vulnerable when conditions and contextual tuples are used with caching enabled.

How do I check if my server is vulnerable to CVE-2024-56323?

Run: docker inspect <openfga-container-id> | grep -E 'OPENFGA.*VERSION|OPENFGA_CHECK_QUERY_CACHE' and cross-reference the version against 1.3.8-1.8.2 range. If caching is enabled and version is in range, you are vulnerable.

What is the workaround if I cannot immediately patch?

There are no known workarounds for this vulnerability. Immediate upgrade to v1.8.3 or higher is required. As a temporary mitigation, consider disabling OPENFGA_CHECK_QUERY_CACHE_ENABLED if operational constraints allow it.

Does Defensia detect CVE-2024-56323?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker or OpenFGA is running on a monitored server, CVE-2024-56323 will appear in your dashboard with remediation steps.

Related Docker CVEs

CVE-2026-57572CVSS 10Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.
CVE-2026-26216CVSS 10Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The __import__ builtin was included in the allowed builtins, allowing unauthenticated remote attackers to import arbitrary modules and execute system commands. Successful exploitation allows full server compromise, including arbitrary command execution, file read and write access, sensitive data exfiltration, and lateral movement within internal networks.
CVE-2026-44329CVSS 10free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's SMF mounts the UPI management route group without OAuth2/bearer-token authorization middleware. A network attacker who can reach SMF on the SBI can hit UPI endpoints with no Authorization header at all, and the requests reach the SMF business handlers. In the running Docker lab this was directly demonstrated for read (GET /upi/v1/upNodesLinks), write (POST /upi/v1/upNodesLinks with attacker-controlled UP-node and link payload), and delete (DELETE /upi/v1/upNodesLinks/{nodeID}) operations. This vulnerability is fixed in 4.2.2.
CVE-2026-42298CVSS 10Postiz is an AI social media scheduling tool. Prior to commit da44801, a "Pwn Request" vulnerability in the Build and Publish PR Docker Image workflow (.github/workflows/pr-docker-build.yml) allows any unauthenticated user to execute arbitrary code during the Docker build process and exfiltrate a highly privileged GITHUB_TOKEN (write-all permissions). This can be achieved simply by opening a Pull Request from a fork with a maliciously modified Dockerfile.dev. This issue has been patched via commit da44801.
CVE-2026-40281CVSS 10Gotenberg is a Docker-powered stateless API for PDF files. In versions 8.30.1 and earlier, the metadata write endpoint validates metadata keys for control characters but leaves metadata values unsanitized. A newline character in a metadata value splits the ExifTool stdin line into two separate arguments, allowing injection of arbitrary ExifTool pseudo-tags such as -FileName, -Directory, -SymLink, and -HardLink. This is a bypass of the incomplete key-sanitization fix introduced in v8.30.1. An unauthenticated attacker can rename or move any PDF being processed to an arbitrary path in the container filesystem, overwrite arbitrary files, or create symlinks and hard links at arbitrary paths.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-56323. Free for 1 server.

Get started free