Every CVE Search/ Get API key

CVE-2025-46569

OPA server Data API HTTP path injection of Rego

7.4 HighFix available

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.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
Low
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
None
Availability
High

Exploit likelihood

0.54%Up 0.5 points since May 2, 2025
90%50%10%1%

What each source reports

CVE List Score used 7.4

OPA server Data API HTTP path injection of Rego

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.

Record
CVE-2025-46569
CVSS 4.0
7.4 HighCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:H/SC:H/SI:H/SA:H
Weakness
CWE-863, CWE-94
Updated
2026-11-02
EUVDEUVD-2025-12838 7.4

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.

Record
EUVD-2025-12838
CVSS 4.0
7.4 HighCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:H/SC:H/SI:H/SA:H
Updated
2026-11-02
GitHub AdvisoriesGHSA-6m8w-jc87-6cr7 7.4

OPA server Data API HTTP path injection of Rego

Impact

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.

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.

Patches

Fixed in OPA v1.4.0.

Workarounds

Don’t publicly expose OPA’s RESTful APIs

Unless necessary for production reasons, network access to OPA’s RESTful APIs should be limited to localhost and/or trusted networks. Since OPA v1.0, unless otherwise configured, the server listener defaults to localhost.

Enable Authentication to Only Allow Access to Trusted Clients

A configured authentication scheme is a requirement when OPA is exposed in an untrusted environment. While requiring authentication alone doesn’t mitigate this attack, it effectively reduces the scope from untrusted clients to trusted clients.

Perform Path Validation Using OPA’s Authorization Policy Functionality

OPA can be configured to use an Authorization Policy to validate all incoming requests. By authoring the Authorization Policy to only accept paths corresponding to expected Rego package references, this attack can be fully mitigated.

The HTTP path in a Data API request is of the format /v1/data/{path:.+} (/v0/data/{path:.+}, for the v0 Data API), where data/{path:.+} directly corresponds to a reference to a virtual document, and a prefix of {path:.+} corresponds to a Rego package declaration. E.g. the HTTP path v1/data/do/re/mi corresponds to the data reference data.do.re.mi, where do.re is the package and mi is the rule in the following Rego module:

package do.re

mi if {
	...
}

Unless otherwise configured, OPA will use the rule at…

Record
GHSA-6m8w-jc87-6cr7
CVSS 4.0
7.4 HighCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:H/SC:H/SI:H/SA:H
Weakness
CWE-78, CWE-94, CWE-770
Updated
2026-11-02
NVD 7.4

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.

Record
CVE-2025-46569
CVSS 4.0
7.4 HighCVSS: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
Weakness
CWE-94, CWE-863
Updated
2026-11-02
OSV 7.4

OPA server Data API HTTP path injection of Rego

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.

Record
CVE-2025-46569
CVSS 4.0
7.4 HighCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:H/SC:H/SI:H/SA:H
Weakness
CWE-863, CWE-94
Updated
2026-11-02
OSVGHSA-6m8w-jc87-6cr7 7.4

OPA server Data API HTTP path injection of Rego

Impact

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.

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.

Patches

Fixed in OPA v1.4.0.

Workarounds

Don’t publicly expose OPA’s RESTful APIs

Unless necessary for production reasons, network access to OPA’s RESTful APIs should be limited to localhost and/or trusted networks. Since OPA v1.0, unless otherwise configured, the server listener defaults to localhost.

Enable Authentication to Only Allow Access to Trusted Clients

A configured authentication scheme is a requirement when OPA is exposed in an untrusted environment. While requiring authentication alone doesn’t mitigate this attack, it effectively reduces the scope from untrusted clients to trusted clients.

Perform Path Validation Using OPA’s Authorization Policy Functionality

OPA can be configured to use an Authorization Policy to validate all incoming requests. By authoring the Authorization Policy to only accept paths corresponding to expected Rego package references, this attack can be fully mitigated.

The HTTP path in a Data API request is of the format /v1/data/{path:.+} (/v0/data/{path:.+}, for the v0 Data API), where data/{path:.+} directly corresponds to a reference to a virtual document, and a prefix of {path:.+} corresponds to a Rego package declaration. E.g. the HTTP path v1/data/do/re/mi corresponds to the data reference data.do.re.mi, where do.re is the package and mi is the rule in the following Rego module:

package do.re

mi if {
	...
}

Unless otherwise configured, OPA will use the rule at…

Record
GHSA-6m8w-jc87-6cr7
CVSS 4.0
7.4 HighCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:H/SC:H/SI:H/SA:H
Weakness
CWE-770, CWE-78, CWE-94
Updated
2026-11-02
Show 11 moreShow less
OSVAZL-63067 No score

CVE-2025-46569 affecting package opa for versions less than 0.63.0-2

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.

Record
AZL-63067
Updated
2026-11-05
OSVGO-2025-3660 No score

OPA server Data API HTTP path injection of Rego in github.com/open-policy-agent/opa

OPA server Data API HTTP path injection of Rego in github.com/open-policy-agent/opa

Record
GO-2025-3660
Updated
2026-11-02
OSVopenSUSE-SU-2025:15059-1 No score

govulncheck-vulndb-0.0.20250506T153719-1.1 on GA media

These are all security issues fixed in the govulncheck-vulndb-0.0.20250506T153719-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2025:15059-1
Updated
2026-11-02
OSVopenSUSE-SU-2025:15253-1 No score

opa-1.6.0-1.1 on GA media

These are all security issues fixed in the opa-1.6.0-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2025:15253-1
Updated
2026-11-02
OSVopenSUSE-SU-2025:15355-1 No score

cosign-2.5.3-1.1 on GA media

These are all security issues fixed in the cosign-2.5.3-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2025:15355-1
Updated
2026-11-02
OSVopenSUSE-SU-2025:15370-1 No score

hauler-1.2.5-1.1 on GA media

These are all security issues fixed in the hauler-1.2.5-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2025:15370-1
Updated
2026-11-02
OSVopenSUSE-SU-2025:15530-1 No score

trivy-0.65.0-2.1 on GA media

These are all security issues fixed in the trivy-0.65.0-2.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2025:15530-1
Updated
2026-11-02
OSVopenSUSE-SU-2025:20117-1 No score

Security update for trivy

This update for trivy fixes the following issues:

Changes in trivy:

Update to version 0.67.2 (bsc#1250625, CVE-2025-11065, bsc#1248897, CVE-2025-58058):

  • fix: Use fetch-level: 1 to check out trivy-repo in the release workflow [backport: release/v0.67] (#9638)
  • fix: restore compatibility for google.protobuf.Value [backport: release/v0.67] (#9631)
  • fix: using SrcVersion instead of Version for echo detector [backport: release/v0.67] (#9629)
  • fix: add buildInfo for BlobInfo in rpc package [backport: release/v0.67] (#9615)
  • fix(vex): don't use reused BOM [backport: release/v0.67] (#9612)
  • fix(vex): don't suppress vulns for packages with infinity loop (#9465)
  • fix(aws): use BuildableClient insead of xhttp.Client (#9436)
  • refactor(misconf): replace github.com/liamg/memoryfs with internal mapfs and testing/fstest (#9282)
  • docs: clarify inline ignore limitations for resource-less checks (#9537)
  • fix(k8s): disable parallel traversal with fs cache for k8s images (#9534)
  • fix(misconf): handle tofu files in module detection (#9486)
  • feat(seal): add seal support (#9370)
  • docs: fix modules path and update code example (#9539)
  • fix: close file descriptors and pipes on error paths (#9536)
  • feat: add documentation URL for database lock errors (#9531)
  • fix(db): Dowload database when missing but metadata still exists (#9393)
  • feat(cloudformation): support default values and list results in Fn::FindInMap (#9515)
  • fix(misconf): unmark cty values before access (#9495)
  • feat(cli): change --list-all-pkgs default to true (#9510)
  • fix(nodejs): parse workspaces as objects for package-lock.json files (#9518)
  • refactor(fs): use underlyingPath to determine virtual files more reliably (#9302)
  • refactor: remove google/wire dependency and implement manual DI (#9509)
  • chore(deps): bump the aws group with 6 updates (#9481)
  • chore(deps): bump the common group across 1 directory with 24 updates (#9507)
  • fix(misconf): wrap legacy ENV values in quotes to preserve spaces (#9497)
  • docs: move info about detection priority into coverage section (#9469)
  • feat(sbom): added support for CoreOS (#9448)
  • fix(misconf): strip build metadata suffixes from image history (#9498)
  • feat(cyclonedx): preserve SBOM structure when scanning SBOM files with vulnerability updates (#9439)
  • docs: Fix typo in terraform docs (#9492)
  • feat(redhat): add os-release detection for RHEL-based images (#9458)
  • ci(deps): add 3-day cooldown period for Dependabot updates (#9475)
  • refactor: migrate from go-json-experiment to encoding/json/v2 (#9422)
  • fix(vuln): compare nuget package names in lower case (#9456)
  • chore: Update release flow to include chocolatey (#9460)
  • docs: document eol supportability (#9434)
  • docs(report): add nuanses about secret/license scanner in summary table (#9442)
  • ci: use environment variables in GitHub Actions for improved security (#9433)
  • chore: bump Go to 1.24.7 (#9435)
  • fix(nodejs): use snapshot string as Package.ID for pnpm packages (#9330)
  • ci(helm): bump Trivy version to 0.66.0 for Trivy Helm Chart 0.18.0 (#9425)

Update to version 0.66.0 (bsc#1248937, CVE-2025-58058):

  • chore(deps): bump the aws group with 7 updates (#9419)
  • refactor(secret): clarify secret scanner messages (#9409)
  • fix(cyclonedx): handle multiple license types (#9378)
  • fix(repo): sanitize git repo URL before inserting into report metadata (#9391)
  • test: add HTTP basic authentication to git test server (#9407)
  • fix(sbom): add support for file component type of CycloneDX (#9372)
  • fix(misconf): ensure module source is known (#9404)
  • ci: migrate GitHub Actions from version tags to SHA pinning (#9405)
  • fix: create temp file under composite fs dir (#9387)
  • chore(deps): bump github.com/ulikunitz/xz from 0.5.12 to 0.5.14 (#9403)
  • refactor: switch to stable azcontainerregistry SDK package (#9319)
  • chore(deps): bump the common…
Record
openSUSE-SU-2025:20117-1
Updated
2026-11-02
OSVopenSUSE-SU-2025:20160-1 No score

Security update for hauler

This update for hauler fixes the following issues:

  • Update to version 1.3.1 (bsc#1251516, CVE-2025-47911, bsc#1251891, CVE-2025-11579, bsc#1251651, CVE-2025-58190, bsc#1248937, CVE-2025-58058):

    • bump github.com/containerd/containerd (#474)
    • another fix to tests for new tests (#472)
    • fixed typo in testdata (#471)
    • fixed/cleaned new tests (#470)
    • trying a new way for hauler testing (#467)
    • update for cosign v3 verify (#469)
    • added digests view to info (#465)
    • bump github.com/nwaples/rardecode/v2 from 2.1.1 to 2.2.0 in the go_modules group across 1 directory (#457)
    • update oras-go to v1.2.7 for security patches (#464)
    • update cosign to v3.0.2+hauler.1 (#463)
    • fixed homebrew directory deprecation (#462)
    • add registry logout command (#460)

  • Update to version 1.3.0:

    • bump the go_modules group across 1 directory with 2 updates (#455)
    • upgraded versions/dependencies/deprecations (#454)
    • allow loading of docker tarballs (#452)
    • bump the go_modules group across 1 directory with 2 updates (#449)

  • update to 1.2.5 (bsc#1246722, CVE-2025-46569):

    • Bump github.com/open-policy-agent/opa from 1.1.0 to 1.4.0 in the go_modules group across 1 directory (CVE-2025-46569)
    • deprecate auth from hauler store copy
    • Bump github.com/cloudflare/circl from 1.3.7 to 1.6.1 in the go_modules group across 1 directory
    • Bump github.com/go-viper/mapstructure/v2 from 2.2.1 to 2.3.0 in the go_modules group across 1 directory
    • upgraded go and dependencies versions

  • Update to version 1.2.5:

    • upgraded go and dependencies versions (#444)
    • Bump github.com/go-viper/mapstructure/v2 (#442)
    • bump github.com/cloudflare/circl (#441)
    • deprecate auth from hauler store copy (#440)
    • Bump github.com/open-policy-agent/opa (#438)

  • update to 1.2.4 (CVE-2025-22872, bsc#1241804):

    • Bump golang.org/x/net from 0.37.0 to 0.38.0 in the go_modules group across 1 directory
    • minor tests updates

  • Update to version 1.2.3:

    • formatting and flag text updates
    • add keyless signature verification (#434)
    • bump helm.sh/helm/v3 in the go_modules group across 1 directory (#430)
    • add --only flag to hauler store copy (for images) (#429)
    • fix tlog verification error/warning output (#428)

  • Update to version 1.2.2 (bsc#1241184, CVE-2024-0406):

    • cleanup new tlog flag typos and add shorthand (#426)
    • default public transparency log verification to false to be airgap friendly but allow override (#425)
    • bump github.com/golang-jwt/jwt/v4 (#423)
    • bump the go_modules group across 1 directory with 2 updates (#422)
    • bump github.com/go-jose/go-jose/v3 (#417)
    • bump github.com/go-jose/go-jose/v4 (#415)
    • clear default manifest name if product flag used with sync (#412)
    • updates for v1.2.0 (#408)
    • fixed remote code (#407)
    • added remote file fetch to load (#406)
    • added remote and multiple file fetch to sync (#405)
    • updated save flag and related logs (#404)
    • updated load flag and related logs [breaking change] (#403)
    • updated sync flag and related logs [breaking change] (#402)
    • upgraded api update to v1/updated dependencies (#400)
    • fixed consts for oci declarations (#398)
    • fix for correctly grabbing platform post cosign 2.4 updates (#393)
    • use cosign v2.4.1+carbide.2 to address containerd annotation in index.json (#390)
    • Bump the go_modules group across 1 directory with 2 updates (#385)
    • replace mholt/archiver with mholt/archives (#384)
    • forked cosign bump to 2.4.1 and use as a library vs embedded binary (#383)
    • cleaned up registry and improved logging (#378)
    • Bump golang.org/x/crypto in the go_modules group across 1 directory (#377)

  • bump net/html dependencies (bsc#1235332, CVE-2024-45338)

  • Update to version 1.1.1:

    • fixed cli desc for store env var (#374)
    • updated versions for go/k8s/helm (#373)
    • updated version flag to internal/flags (#369)
    • renamed incorrectly named consts (#371)
    • added store env var (#370) …
Record
openSUSE-SU-2025:20160-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:20798-1 No score

Security update for trivy

This update for trivy fixes the following issues:

Update to version 0.68.2:

Security fixes:

  • CVE-2024-3817: hashicorp/go-getter: argument injection when fetching remote default git branches (bsc#1227010).
  • CVE-2024-45337: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto (bsc#1234512).
  • CVE-2024-45338: golang.org/x/net/html: denial of service due to non-linear parsing of case-insensitive content (bsc#1235265).
  • CVE-2024-51744: github.com/golang-jwt/jwt/v4: Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations in golang-jwt (bsc#1232948).
  • CVE-2025-11065: github.com/go-viper/mapstructure/v2: sensitive Information leak in logs (bsc#1250625).
  • CVE-2025-22868: golang.org/x/oauth2/jws: Unexpected memory consumption during token parsing in golang.org/x/oauth2 (bsc#1239225).
  • CVE-2025-22869: golang.org/x/crypto/ssh: Denial of Service in the Key Exchange of golang.org/x/crypto/ssh (bsc#1239385).
  • CVE-2025-22872: golang.org/x/net/html: incorrectly interpreted tags can cause content to be placed wrong scope during DOM construction (bsc#1241724).
  • CVE-2025-27144: gopkg.in/go-jose/go-jose.v2: Go JOSE's Parsing Vulnerable to Denial of Service (bsc#1237618).
  • CVE-2025-30204: github.com/golang-jwt/jwt/v4,github.com/golang-jwt/jwt/v5: jwt-go allows excessive memory allocation during header parsing (bsc#1240466).
  • CVE-2025-46569: github.com/open-policy-agent/opa: HTTP request path can be crafted to inject Rego code into a constructed query when a virtual document is requested through the Data API (bsc#1246730).
  • CVE-2025-47291: github.com/containerd/containerd/v2: Incorrect cgroup hierarchy assignment for containers running in usernamespaced Kubernetes pods. (bsc#1243633).
  • CVE-2025-47911: golang.org/x/net/html: various algorithms with quadratic complexity when parsing HTML documents (bsc#1251363).
  • CVE-2025-47913: golang.org/x/crypto/ssh/agent: client process termination when receiving an unexpected message type in response to a key listing or signing request (bsc#1253512).
  • CVE-2025-47914: golang.org/x/crypto/ssh/agent: non validated message size can cause a panic due to an out of bounds read (bsc#1253977).
  • CVE-2025-53547: helm.sh/helm/v3: Helm Chart Code Execution (bsc#1246151).
  • CVE-2025-58058: github.com/ulikunitz/xz: github.com/ulikunitz/xz leaks memory (bsc#1248937, bsc#1248897).
  • CVE-2025-58181: golang.org/x/crypto/ssh: invalidated number of mechanisms can cause unbounded memory consumption (bsc#1253786).
  • CVE-2025-58190: golang.org/x/net/html: excessive memory consumption by html.ParseFragment when processing specially crafted input (bsc#1251547).

Other fixes:

  • Update installation.md (#8979)
  • chore(alpine): add EOL date for Alpine 3.21 (#8221)
  • chore(alpine): add EOL date for Alpine 3.22 (#8992)
  • chore(cli): Remove Trivy Cloud (#9847)
  • chore(deps): Bump trivy-checks (#7819)
  • chore(deps): Bump trivy-checks (#8310)
  • chore(deps): Bump trivy-checks (#8619)
  • chore(deps): Bump trivy-checks (#8934)
  • chore(deps): Bump trivy-checks to v1.7.1 (#8467)
  • chore(deps): Bump up trivy-checks to v1.3.0 (#7959)
  • chore(deps): Switch to go-viper/mapstructure (#9579)
  • chore(deps): Update trivy-checks (#8798)
  • chore(deps): Upgrade trivy-checks (#8018)
  • chore(deps): bump Go to v1.23.5 (#8341)
  • chore(deps): bump Go to v1.23.5 [backport: release/v0.59] (#8343)
  • chore(deps): bump github.com/CycloneDX/cyclonedx-go from v0.9.1 to v0.9.2 (#8105)
  • chore(deps): bump github.com/CycloneDX/cyclonedx-go from v0.9.1 to v0.9.2 [backport: release/v0.58] (#8136)
  • chore(deps): bump golang.org/x/net from v0.32.0 to v0.33.0 (#8140)
  • chore(deps): bump golang.org/x/net from v0.32.0 to v0.33.0 [backport: release/v0.58] (#8142)
  • chore(deps): bump alpine from 3.20.0 to 3.21.0 in the docker group across 1 directory (#8196)
  • chore(deps): bump alpine from…
Record
openSUSE-SU-2026:20798-1
Updated
2026-11-02
OSVSUSE-SU-2025:02592-1 No score

Security update for cosign

This update for cosign fixes the following issues:

Update to version 2.5.3 (jsc#SLE-23879):

  • CVE-2025-46569: Fixed OPA server Data API HTTP path injection of Rego (bsc#1246725)

Changelog:

Update to 2.5.3:

  • Add signing-config create command (#4280)
  • Allow multiple services to be specified for trusted-root create (#4285)
  • force when copying the latest image to overwrite (#4298)
  • Fix cert verification logic for trusted-root/SCTs (#4294)
  • Fix lint error for types package (#4295)
  • feat: Add OCI 1.1+ experimental support to tree (#4205)
  • Add validity period end for trusted-root create (#4271)
  • avoid double-loading trustedroot from file (#4264)

Update to 2.5.2:

  • Do not load trusted root when CT env key is set
  • docs: improve doc for --no-upload option (#4206)

Update to 2.5.1:

  • Add Rekor v2 support for trusted-root create (#4242)
  • Add baseUrl and Uri to trusted-root create command
  • Upgrade to TUF v2 client with trusted root
  • Don't verify SCT for a private PKI cert (#4225)
  • Bump TSA library to relax EKU chain validation rules (#4219)
  • Bump sigstore-go to pick up log index=0 fix (#4162)
  • remove unused recursive flag on attest command (#4187)
Record
SUSE-SU-2025:02592-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
github.com/open-policy-agent/opa/v1/server
Go
 before 1.4.0
1.4.0
github.com/open-policy-agent/opa/server
Go
 before 1.4.0
1.4.0
github.com/open-policy-agent/opa
Go
 before 1.4.0
1.4.0
opa
Azure Linux:3
 before 0.63.0-2
0.63.0-2
cosign
SUSE:Linux Enterprise Module for Basesystem 15 SP6
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
cosign
SUSE:Linux Enterprise Module for Basesystem 15 SP7
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
cosign
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
cosign
SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
cosign
SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
cosign
SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
Show 13 moreShow less
Affected packages
PackageAffectedFixed
cosign
SUSE:Linux Enterprise Server 15 SP4-LTSS
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
cosign
SUSE:Linux Enterprise Server 15 SP5-LTSS
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
cosign
SUSE:Linux Enterprise Server for SAP Applications 15 SP4
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
cosign
SUSE:Linux Enterprise Server for SAP Applications 15 SP5
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
cosign
SUSE:Manager Proxy 4.3
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
cosign
SUSE:Manager Server 4.3
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
cosign
openSUSE:Leap 15.6
 before 2.5.3-150400.3.30.1
2.5.3-150400.3.30.1
govulncheck-vulndb
openSUSE:Tumbleweed
From an advisory covering 12 CVEs
 before 0.0.20250506T153719-1.1
0.0.20250506T153719-1.1
opa
openSUSE:Tumbleweed
From an advisory covering 2 CVEs
 before 1.6.0-1.1
1.6.0-1.1
cosign
openSUSE:Tumbleweed
 before 2.5.3-1.1
2.5.3-1.1
hauler
openSUSE:Tumbleweed
 before 1.2.5-1.1
1.2.5-1.1
trivy
openSUSE:Tumbleweed
 before 0.65.0-2.1
0.65.0-2.1
hauler
openSUSE:Leap 16.0
From an advisory covering 8 CVEs
 before 1.3.1-bp160.1.1
1.3.1-bp160.1.1

History

History
RecordedChangedSources
affected
factsOSV
affected
first indexedCVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2025-46569 is a high vulnerability (CVSS 7.4) in Open-policy-agent Opa, published May 1, 2025. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.54%, the 45th percentile. Fixed in github.com/open-policy-agent/opa/v1/server 1.4.0.

References

Show 66 moreShow less
This page doesn't list everything

Left out here: the rest of 5 source descriptions. The JSON record has them.

Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open