# CVE-2022-36085: OPA Compiler: Bypass of WithUnsafeBuiltins using `with` keyword to mock functions

> Attackers can bypass unsafe builtin restrictions in OPA by mocking functions, requiring non-default configuration to exploit.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Sep 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-f524-rf33-2jjr, GO-2022-0978

## What is CVE-2022-36085?

CVE-2022-36085 is a high-severity vulnerability in open-policy-agent opa, published on 8 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Open Policy Agent (OPA) is an open source, general-purpose policy engine. The Rego compiler provides a (deprecated) `WithUnsafeBuiltins` function, which allows users to provide a set of built-in functions that should be deemed unsafe — and as such rejected — by the compiler if encountered in the policy compilation stage. A bypass of this protection has been found, where the use of the `with` keyword to mock such a built-in function (a feature introduced in OPA v0.40.0), isn’t taken into account by `WithUnsafeBuiltins`. Multiple conditions need to be met in order to create an adverse effect. Version 0.43.1 contains a patch for this issue. As a workaround, avoid using the `WithUnsafeBuiltins` function and use the `capabilities` feature instead.

Weakness: CWE-693 (Protection Mechanism Failure), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-36085?

3 open source packages ship an affected version, including github.com/open-policy-agent/opa. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/open-policy-agent/opa` | Go | From 0.40.0 | 0.43.1 |
| `github.com/open-policy-agent/opa` | Go | From 0.40.0 | 0.43.1 |
| `github.com/open-policy-agent/opa` | Go | From 0.40.0 | 0.44.0 |

Products: Openpolicyagent Open Policy Agent.

## How do I fix CVE-2022-36085?

Upgrade github.com/open-policy-agent/opa to a fixed version for your release line: 0.43.1 or 0.44.0.

## Is CVE-2022-36085 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36085 exists.

## Other vulnerabilities in open-policy-agent opa

- [CVE-2022-33082](https://insights.sbomify.com/CVE-2022-33082/): Denial of service in Open Policy Agent (high 7.5)
- [CVE-2022-28946](https://insights.sbomify.com/CVE-2022-28946/): Out of bounds memory access in github.com/open-policy-agent/opa (high 7.5)
- [CVE-2022-23628](https://insights.sbomify.com/CVE-2022-23628/): Array literal misordering in github.com/open-policy-agent/opa (medium 6.3)
- [CVE-2024-8260](https://insights.sbomify.com/CVE-2024-8260/): OPA SMB Force-Authentication (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36085 and fix it if it is affected.

What it is: CVE-2022-36085 is a high-severity vulnerability in open-policy-agent opa, published on 8 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36085 exists.

Affected packages and fixed versions:
- github.com/open-policy-agent/opa (Go): affected from 0.40.0; fixed in 0.43.1
- github.com/open-policy-agent/opa (Go): affected from 0.40.0; fixed in 0.43.1
- github.com/open-policy-agent/opa (Go): affected from 0.40.0; fixed in 0.44.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-36085/ (Markdown: https://insights.sbomify.com/CVE-2022-36085/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-36085
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-36085
- OSV: https://osv.dev/vulnerability/CVE-2022-36085

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-36085/
Summaries are generated and may contain mistakes; the official description above is the record.