CVE-2022-36085Public exploitNetwork attack vector

Unsafe built-in execution via unchecked with replacement

Published Sep 8, 2022 · Updated Apr 22, 2025

Protection bypass in OPA 0.40.0 through 0.43.0 allows attackers to invoke forbidden built-ins through untrusted Rego policies. The Rego compiler's WithUnsafeBuiltins and rego.UnsafeBuiltins paths fail to check a with replacement against the unsafe-built-in map, allowing a safe function to resolve to http.send or opa.runtime. Impact requires a Go API integration that evaluates attacker-supplied policy with unsafe built-ins configured, or a public Query API relying on that restriction; bypass enables outbound requests or disclosure of runtime configuration and environment variables.

CVSS severity7.4
High
EPSS probability1.56%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Protection bypass in OPA 0.40.0 through 0.43.0 allows attackers to invoke forbidden built-ins through untrusted Rego policies. The Rego compiler's WithUnsafeBuiltins and rego.UnsafeBuiltins paths fail to check a with replacement against the unsafe-built-in map, allowing a safe function to resolve to http.send or opa.runtime. Impact requires a Go API integration that evaluates attacker-supplied policy with unsafe built-ins configured, or a public Query API relying on that restriction; bypass enables outbound requests or disclosure of runtime configuration and environment variables.

The record

CVE
CVE-2022-36085
Published
Sep 8, 2022
Updated
Apr 22, 2025
Vendor
Open Policy Agent
Product
Open Policy Agent (OPA)
Classifications
CWE-693, CWE-20, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 8, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 22, 2025Record 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.

  1. Affected versionversion=>= 0.40.0, < 0.43.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Open Policy Agent · Open Policy Agent (OPA)version=>= 0.40.0, < 0.43.1

Published CVSS scores

9.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
7.4GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-693Protection Mechanism Failure
CWE-20Improper Input Validation
T1190Exploit Public-Facing Application

Public exploit references

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