Sourced from github.com/open-policy-agent/opa's releases.
v1.4.2
This is a bug fix release addressing the missing
capabilities/v1.4.1.json
in the v1.4.1 release.v1.4.1
⚠️ Please skip this release and go straight to v1.4.2 ⚠️ This release is broken due to a mistake during the release process and the artifacts are missing a crucial capabilities file. Sorry for any inconvenience.
This is a security fix release for the fixes published in Go 1.24.1 and 1.24.2
- build: bump go to 1.24.2 (#7544) (authored by
@sspaink
) AddressingCVE-2025-22870
andCVE-2025-22871
vulnerabilities in the Go runtime.v1.4.0
This release contains a security fix addressing CVE-2025-46569. It also includes a mix of new features, bugfixes, and dependency updates.
Security Fix: CVE-2025-46569 - OPA server Data API HTTP path injection of Rego (GHSA-6m8w-jc87-6cr7)
A vulnerability in the OPA server's Data API allows an attacker to craft the HTTP path in a way that injects Rego code into the query that is evaluated.
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.Users are only impacted if all of the following apply:
- OPA is deployed as a standalone server (rather than being used as a Go library)
- The OPA server is exposed outside of the local host in an untrusted environment.
- The configured authorization policy does not do exact matching of the input.path attribute when deciding if the request should be allowed.
or, if all of the following apply:
- OPA is deployed as a standalone server.
- The service connecting to OPA allows 3rd parties to insert unsanitised text into the path of the HTTP request to OPA’s Data API.
Note: With no Authorization Policy configured for restricting API access (the default configuration), the RESTful Data API provides access for managing Rego policies; and the RESTful Query API facilitates advanced queries. Full access to these APIs provides both simpler, and broader access than what the security issue describes here can facilitate. As such, OPA servers exposed to a network are not considered affected by the attack described here if they are knowingly not restricting access through an Authorization Policy.
This issue affects all versions of OPA prior to 1.4.0.
See the Security Advisory for more details.
Reported by
@GamrayW
,@HyouKash
,@AdrienIT
, authored by@johanfylling
Runtime, Tooling, SDK
... (truncated)
Sourced from github.com/open-policy-agent/opa's changelog.
1.4.2
This is a bug fix release addressing the missing
capabilities/v1.4.1.json
in the v1.4.1 release.1.4.1
This is a security fix release for the fixes published in Go 1.24.1 and 1.24.2
- build: bump go to 1.24.2 (#7544) (authored by
@sspaink
) AddressingCVE-2025-22870
andCVE-2025-22871
vulnerabilities in the Go runtime.1.4.0
This release contains a security fix addressing CVE-2025-46569. It also includes a mix of new features, bugfixes, and dependency updates.
Security Fix: CVE-2025-46569 - OPA server Data API HTTP path injection of Rego (GHSA-6m8w-jc87-6cr7)
A vulnerability in the OPA server's Data API allows an attacker to craft the HTTP path in a way that injects Rego code into the query that is evaluated.
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.Users are only impacted if all of the following apply:
- OPA is deployed as a standalone server (rather than being used as a Go library)
- The OPA server is exposed outside of the local host in an untrusted environment.
- The configured authorization policy does not do exact matching of the input.path attribute when deciding if the request should be allowed.
or, if all of the following apply:
- OPA is deployed as a standalone server.
- The service connecting to OPA allows 3rd parties to insert unsanitised text into the path of the HTTP request to OPA’s Data API.
Note: With no Authorization Policy configured for restricting API access (the default configuration), the RESTful Data API provides access for managing Rego policies; and the RESTful Query API facilitates advanced queries. Full access to these APIs provides both simpler, and broader access than what the security issue describes here can facilitate. As such, OPA servers exposed to a network are not considered affected by the attack described here if they are knowingly not restricting access through an Authorization Policy.
This issue affects all versions of OPA prior to 1.4.0.
See the Security Advisory for more details.
Reported by
@GamrayW
,@HyouKash
,@AdrienIT
, authored by@johanfylling
Runtime, Tooling, SDK
- ast: Adding
rego_v1
feature to--v0-compatible
capabilities (#7474) authored by@johanfylling
- executable: Add version and icon to OPA windows executable (#3171) authored by
@sspaink
reported by@christophwille
- format: Don't panic on format due to unexpected comments (#6330) authored by
@sspaink
reported by@sirpi
- format: Avoid modifying strings when formatting (#6220) authored by
@sspaink
reported by@zregvart
- plugins/status: FIFO buffer channel for status events to prevent slow status API blocking (#7522) authored by
@sspaink
... (truncated)
5e4582b
Prepare v1.4.2 release (#7547)3b64aff
Patch release v1.4.1 (#7545)8b07202
Prepare v1.4.0 release (#7541)ad20632
Merge commit from fork24ff9cf
fix: return the raw strings when formatting (#7525)254f3bf
fix(status plugin): make sure the latest status is read before manually
trigg...9b5f601
docs: fix post merge badge (#7532)e490277
docs: Point path versioned requests to new sites (#7531)d65888c
plugins/status: FIFO buffer channel for status events to prevent slow
status ...eb77d10
docs: update edge links to use /docs/edge/ path (#7529)