NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 29/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.54% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: open-policy-agent opa 1.4.0; azl3 opa 0.63.0-2 on Azure Linux 3.0 0.63.0-2.

Low priority for now. Upgrade to open-policy-agent opa 1.4.0; azl3 opa 0.63.0-2 on Azure Linux 3.0 0.63.0-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.4 · v4.0—No exploit Fix available

Published: May 1, 2025
Updated: Jun 17, 2026
EPSS: 0.5% · 45th percentile
CWE: CWE-94

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 29 / 40 · 7.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.5%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 7.4; NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

open-policy-agent opa
- < 1.4.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/open-policy-agent/opa	before 1.4.0	1.4.0
Go	github.com/open-policy-agent/opa/server	before 1.4.0	1.4.0
Go	github.com/open-policy-agent/opa/v1/server	before 1.4.0	1.4.0
openSUSE:Leap 15.6	cosign	before 2.5.3-150400.3.30.1	2.5.3-150400.3.30.1
openSUSE:Leap 16.0	hauler	before 1.3.1-bp160.1.1	1.3.1-bp160.1.1
openSUSE:Tumbleweed	cosign	before 2.5.3-1.1	2.5.3-1.1
openSUSE:Tumbleweed	govulncheck-vulndb	before 0.0.20250506T153719-1.1	0.0.20250506T153719-1.1
openSUSE:Tumbleweed	hauler	before 1.2.5-1.1	1.2.5-1.1
openSUSE:Tumbleweed	opa	before 1.6.0-1.1	1.6.0-1.1
openSUSE:Tumbleweed	trivy	before 0.65.0-2.1	0.65.0-2.1
SUSE:Linux Enterprise Module for Basesystem 15 SP6	cosign	before 2.5.3-150400.3.30.1	2.5.3-150400.3.30.1

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
open-policy-agent opa	1.4.0 · description	Vendor (CNA)
azl3 opa 0.63.0-2 on Azure Linux 3.0	0.63.0-2 · CBL-Mariner Releases	Microsoft (MSRC)
Go:github.com/open-policy-agent/opa	1.4.0	Package registry (OSV)
Go:github.com/open-policy-agent/opa/server	1.4.0	Package registry (OSV)
Go:github.com/open-policy-agent/opa/v1/server	1.4.0	Package registry (OSV)
opensuse:cosign	2.5.3-150400.3.30.1 · openSUSE:Leap 15.6	Package registry (OSV)
opensuse:govulncheck-vulndb	0.0.20250506T153719-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:hauler	1.2.5-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:opa	1.6.0-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:trivy	0.65.0-2.1 · openSUSE:Tumbleweed	Package registry (OSV)
suse:cosign	2.5.3-150400.3.30.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

open-policy-agent/opacommit ad20632

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: X

Weakness class (CWE)

CWE-94 · Improper Control of Generation of Code ('Code Injection')

CVSS 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary