{"id":"CVE-2024-29903","aliases":["BIT-cosign-2024-29903","EUVD-2024-1167","GHSA-95pr-fxf5-86gv","GO-2024-2719","RHEA-2024:4022","SUSE-SU-2024:1486-1","SUSE-SU-2024:1486-2","openSUSE-SU-2024:13863-1"],"status":"published","title":"Cosign vulnerable to machine-wide denial of service via malicious artifacts","description":"Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, maliciously-crafted software artifacts can cause denial of service of the machine running Cosign thereby impacting all services on the machine. The root cause is that Cosign creates slices based on the number of signatures, manifests or attestations in untrusted artifacts. As such, the untrusted artifact can control the amount of memory that Cosign allocates. The exact issue is Cosign allocates excessive memory on the lines that creates a slice of the same length as the manifests. Version 2.2.4 contains a patch for the vulnerability.","severity":{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00851,"percentile":0.58643,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-770"],"published":"2024-04-10T22:30:50Z","modified":"2026-10-28T02:31:03Z","fixes":[{"ecosystem":"Go","package":"github.com/sigstore/cosign/v2","fixed_in":["2.2.4"],"sources":["ghsa","osv"]},{"ecosystem":"Bitnami","package":"cosign","fixed_in":["2.2.4"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/sigstore/cosign","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.2.3"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/sigstore/cosign/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.2.3"},{"fixed":"2.2.4"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"cosign","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.2.4"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/sigstore/cosign","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"2.2.3"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/sigstore/cosign/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.2.4"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/sigstore/cosign","ranges":[{"type":"SEMVER","events":[{"introduced":"0"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/sigstore/cosign/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.2.4"}]}]},{"source":"osv","ecosystem":"Red Hat:openshift_pipelines:1.15::el8","package":"openshift-pipelines-client","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.15.0-11496.el8"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openshift_pipelines:1.15::el8","package":"openshift-pipelines-client-redistributable","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.15.0-11496.el8"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP5","package":"cosign","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.4-150400.3.20.1"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"cosign","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.4-150400.3.20.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP6","package":"cosign","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.4-150400.3.20.1"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Leap 15.6","package":"cosign","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.4-150400.3.20.1"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"cosign","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.4-1.1"}]}],"bundled":2}],"products":[{"vendor":"sigstore","product":"cosign"}],"references":[{"url":"https://github.com/sigstore/cosign/security/advisories/GHSA-95pr-fxf5-86gv","tags":["x_refsource_CONFIRM","x_transferred","Exploit","Vendor Advisory","advisory","web","article"]},{"url":"https://github.com/sigstore/cosign/commit/629f5f8fa672973503edde75f84dcd984637629e","tags":["x_refsource_MISC","x_transferred","Patch","fix","web"]},{"url":"https://github.com/sigstore/cosign/blob/14795db16417579fac0c00c11e166868d7976b61/pkg/cosign/verify.go#L948-L955","tags":["x_refsource_MISC","x_transferred","Product","web"]},{"url":"https://github.com/sigstore/cosign/blob/286a98a4a99c1b2f32f84b0d560e324100312280/pkg/oci/remote/signatures.go#L56-L70","tags":["x_refsource_MISC","x_transferred","Product","web"]},{"url":"https://github.com/sigstore/cosign/releases/tag/v2.2.4","tags":["x_refsource_MISC","x_transferred","Release Notes","article","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-29903","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-95pr-fxf5-86gv"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/29xxx/CVE-2024-29903.json","tags":["advisory"]},{"url":"https://github.com/sigstore/cosign","tags":["package"]},{"url":"https://access.redhat.com/errata/RHEA-2024:4022","tags":["advisory"]},{"url":"https://docs.openshift.com/container-platform/4.14/cli_reference/tkn_cli/installing-tkn.html","tags":["article"]},{"url":"https://issues.redhat.com/browse/SRVKP-3124","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2024/rhea-2024_4022.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2023-45288","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268273","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2023-45288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-45288","tags":["advisory"]},{"url":"https://nowotarski.info/http2-continuation-flood/","tags":["article"]},{"url":"https://pkg.go.dev/vuln/GO-2024-2687","tags":["advisory"]},{"url":"https://www.kb.cert.org/vuls/id/421644","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-28110","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268372","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-28110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-28110","tags":["advisory"]},{"url":"https://github.com/cloudevents/sdk-go/security/advisories/GHSA-5pf6-2qwx-pxm2","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-28180","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2268854","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-28180","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-28180","tags":["advisory"]},{"url":"https://github.com/go-jose/go-jose/security/advisories/GHSA-c5q2-7r4c-mv6g","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-29902","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2274508","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-29902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-29902","tags":["advisory"]},{"url":"https://github.com/sigstore/cosign/security/advisories/GHSA-88jx-383q-w4qc","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2024-29903","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2274504","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2024-29903","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241486-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1222835","tags":["report"]},{"url":"https://bugzilla.suse.com/1222837","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-29902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-29903","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2024/suse-su-20241486-2/","tags":["advisory"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2024-29903","title":"Cosign vulnerable to machine-wide denial of service via malicious artifacts","description":"Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, maliciously-crafted software artifacts can cause denial of service of the machine running Cosign thereby impacting all services on the machine. The root cause is that Cosign creates slices based on the number of signatures, manifests or attestations in untrusted artifacts. As such, the untrusted artifact can control the amount of memory that Cosign allocates. The exact issue is Cosign allocates excessive memory on the lines that creates a slice of the same length as the manifests. Version 2.2.4 contains a patch for the vulnerability.","status":"published","published":"2024-04-10T22:30:50.89Z","modified":"2024-08-02T01:17:58.6Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium","assessor":"cna"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:34:14.985673Z"}],"euvd":[{"id":"EUVD-2024-1167","description":"Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, maliciously-crafted software artifacts can cause denial of service of the machine running Cosign thereby impacting all services on the machine. The root cause is that Cosign creates slices based on the number of signatures, manifests or attestations in untrusted artifacts. As such, the untrusted artifact can control the amount of memory that Cosign allocates. The exact issue is Cosign allocates excessive memory on the lines that creates a slice of the same length as the manifests. Version 2.2.4 contains a patch for the vulnerability.","status":"published","published":"2024-04-10T22:30:50Z","modified":"2024-08-02T01:17:58Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-03T03:50:25.628684Z"}],"ghsa":[{"id":"GHSA-95pr-fxf5-86gv","title":"Cosign malicious artifacts can cause machine-wide DoS","description":"Maliciously-crafted software artifacts can cause denial of service of the machine running Cosign, thereby impacting all services on the machine. The root cause is that Cosign creates slices based on the number of signatures, manifests or attestations in untrusted artifacts. As such, the untrusted artifact can control the amount of memory that Cosign allocates.  \n\nAs an example, these lines demonstrate the problem:\n\nhttps://github.com/sigstore/cosign/blob/286a98a4a99c1b2f32f84b0d560e324100312280/pkg/oci/remote/signatures.go#L56-L70 \n\nThis `Get()` method gets the manifest of the image, allocates a slice equal to the length of the layers in the manifest, loops through the layers and adds a new signature to the slice.\n\nThe exact issue is Cosign allocates excessive memory on the lines that creates a slice of the same length as the manifests. \n\n## Remediation\n\nUpdate to the latest version of Cosign, where the number of attestations, signatures and manifests has been limited to a reasonable value.\n\n## Cosign PoC\n\nIn the case of this API (also referenced above):\n\nhttps://github.com/sigstore/cosign/blob/286a98a4a99c1b2f32f84b0d560e324100312280/pkg/oci/remote/signatures.go#L56-L70\n\n… The first line can contain a length that is safe for the system and will not throw a runtime panic or be blocked by other safety mechanisms. For the sake of argument, let’s say that the length of `m, err := s.Manifest()` is the max allowed (by the machine without throwing OOM panics) manifests minus 1. When Cosign then allocates a new slice on this line: `signatures := make([]oci.Signature, 0, len(m.Layers))`, Cosign will allocate more memory than is available and the machine will be denied of service, causing Cosign and all other services on the machine to be unavailable.\n\nTo illustrate the issue here, we run a modified version of `TestSignedImageIndex()` in `pkg/oci/remote`:\n\nhttps://github.com/sigstore/cosign/blob/14795db16417579fac0c00c11e166868d7976b61/pkg/oci/remote/index_test.go#L31-L57\n\nHere, `wantLayers` is the number of manifests from these lines:\n\nhttps://github.com/sigstore/cosign/blob/286a98a4a99c1b2f32f84b0d560e324100312280/pkg/oci/remote/signatures.go#L56-L60\n\nTo test this, we want to make `wantLayers` high enough to not cause a memory on its own but still trigger the machine-wide OOM when a slice gets create with the same length. On my local machine, it would take hours to create a slice of layers that fulfils that criteria, so instead I modify the Cosign production code to reflect a long list of manifests:\n\n```golang\n// Get implements oci.Signatures\nfunc (s *sigs) Get() ([]oci.Signature, error) {\n        m, err := s.Manifest()\n        if err != nil {\n                return nil, err\n        }\n        // Here we imitate a long list of manifests\n        ms := make([]byte, 2600000000) // imitate a long list of manifests\n        signatures := make([]oci.Signature, 0, len(ms))\n        panic(\"Done\")\n        //signatures := make([]oci.Signature, 0, len(m.Layers))\n        for _, desc := range m.Layers {\n```\n\nWith this modified code, if we can cause an OOM without triggering the `panic(\"Done\")`, we have succeeded.","status":"published","published":"2024-04-11T17:15:46Z","modified":"2024-04-11T17:15:54Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:37:42.744468Z"}],"nvd":[{"id":"CVE-2024-29903","description":"Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, maliciously-crafted software artifacts can cause denial of service of the machine running Cosign thereby impacting all services on the machine. The root cause is that Cosign creates slices based on the number of signatures, manifests or attestations in untrusted artifacts. As such, the untrusted artifact can control the amount of memory that Cosign allocates. The exact issue is Cosign allocates excessive memory on the lines that creates a slice of the same length as the manifests. Version 2.2.4 contains a patch for the vulnerability.","status":"published","published":"2024-04-10T23:15:07.13Z","modified":"2026-06-17T07:23:20.263Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium","assessor":"secondary"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T14:09:49.255123Z"}],"osv":[{"id":"CVE-2024-29903","title":"Cosign vulnerable to machine-wide denial of service via malicious artifacts","description":"Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, maliciously-crafted software artifacts can cause denial of service of the machine running Cosign thereby impacting all services on the machine. The root cause is that Cosign creates slices based on the number of signatures, manifests or attestations in untrusted artifacts. As such, the untrusted artifact can control the amount of memory that Cosign allocates. The exact issue is Cosign allocates excessive memory on the lines that creates a slice of the same length as the manifests. Version 2.2.4 contains a patch for the vulnerability.","status":"published","published":"2024-04-10T22:30:50.89Z","modified":"2026-10-28T02:31:03.854362731Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:44:40.06138Z"},{"id":"GHSA-95pr-fxf5-86gv","title":"Cosign malicious artifacts can cause machine-wide DoS","description":"Maliciously-crafted software artifacts can cause denial of service of the machine running Cosign, thereby impacting all services on the machine. The root cause is that Cosign creates slices based on the number of signatures, manifests or attestations in untrusted artifacts. As such, the untrusted artifact can control the amount of memory that Cosign allocates.  \n\nAs an example, these lines demonstrate the problem:\n\nhttps://github.com/sigstore/cosign/blob/286a98a4a99c1b2f32f84b0d560e324100312280/pkg/oci/remote/signatures.go#L56-L70 \n\nThis `Get()` method gets the manifest of the image, allocates a slice equal to the length of the layers in the manifest, loops through the layers and adds a new signature to the slice.\n\nThe exact issue is Cosign allocates excessive memory on the lines that creates a slice of the same length as the manifests. \n\n## Remediation\n\nUpdate to the latest version of Cosign, where the number of attestations, signatures and manifests has been limited to a reasonable value.\n\n## Cosign PoC\n\nIn the case of this API (also referenced above):\n\nhttps://github.com/sigstore/cosign/blob/286a98a4a99c1b2f32f84b0d560e324100312280/pkg/oci/remote/signatures.go#L56-L70\n\n… The first line can contain a length that is safe for the system and will not throw a runtime panic or be blocked by other safety mechanisms. For the sake of argument, let’s say that the length of `m, err := s.Manifest()` is the max allowed (by the machine without throwing OOM panics) manifests minus 1. When Cosign then allocates a new slice on this line: `signatures := make([]oci.Signature, 0, len(m.Layers))`, Cosign will allocate more memory than is available and the machine will be denied of service, causing Cosign and all other services on the machine to be unavailable.\n\nTo illustrate the issue here, we run a modified version of `TestSignedImageIndex()` in `pkg/oci/remote`:\n\nhttps://github.com/sigstore/cosign/blob/14795db16417579fac0c00c11e166868d7976b61/pkg/oci/remote/index_test.go#L31-L57\n\nHere, `wantLayers` is the number of manifests from these lines:\n\nhttps://github.com/sigstore/cosign/blob/286a98a4a99c1b2f32f84b0d560e324100312280/pkg/oci/remote/signatures.go#L56-L60\n\nTo test this, we want to make `wantLayers` high enough to not cause a memory on its own but still trigger the machine-wide OOM when a slice gets create with the same length. On my local machine, it would take hours to create a slice of layers that fulfils that criteria, so instead I modify the Cosign production code to reflect a long list of manifests:\n\n```golang\n// Get implements oci.Signatures\nfunc (s *sigs) Get() ([]oci.Signature, error) {\n        m, err := s.Manifest()\n        if err != nil {\n                return nil, err\n        }\n        // Here we imitate a long list of manifests\n        ms := make([]byte, 2600000000) // imitate a long list of manifests\n        signatures := make([]oci.Signature, 0, len(ms))\n        panic(\"Done\")\n        //signatures := make([]oci.Signature, 0, len(m.Layers))\n        for _, desc := range m.Layers {\n```\n\nWith this modified code, if we can cause an OOM without triggering the `panic(\"Done\")`, we have succeeded.","status":"published","published":"2024-04-11T17:15:46Z","modified":"2026-09-10T03:50:00.260031952Z","cvss":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-770"],"updated_at":"2026-11-02T15:46:43.123867Z"},{"id":"RHEA-2024:4022","title":"Red Hat Enhancement Advisory: Red Hat OpenShift Pipelines Client tkn for 1.15.0 release","status":"published","published":"2025-02-26T10:05:17Z","modified":"2026-10-16T10:03:20Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:58.636919Z"},{"id":"BIT-cosign-2024-29903","title":"Cosign vulnerable to machine-wide denial of service via malicious artifacts","description":"Cosign provides code signing and transparency for containers and binaries. Prior to version 2.2.4, maliciously-crafted software artifacts can cause denial of service of the machine running Cosign thereby impacting all services on the machine. The root cause is that Cosign creates slices based on the number of signatures, manifests or attestations in untrusted artifacts. As such, the untrusted artifact can control the amount of memory that Cosign allocates. The exact issue is Cosign allocates excessive memory on the lines that creates a slice of the same length as the manifests. Version 2.2.4 contains a patch for the vulnerability.","status":"published","published":"2024-04-12T07:17:12.054Z","modified":"2026-09-08T08:46:05.154792043Z","updated_at":"2026-11-02T15:28:28.70813Z"},{"id":"GO-2024-2719","title":"Cosign malicious artifacts can cause machine-wide DoS in github.com/sigstore/cosign","description":"Cosign malicious artifacts can cause machine-wide DoS in github.com/sigstore/cosign","status":"published","published":"2024-06-05T15:10:52Z","modified":"2026-02-04T02:35:06.535922Z","updated_at":"2026-11-02T15:47:01.453823Z"},{"id":"openSUSE-SU-2024:13863-1","title":"cosign-2.2.4-1.1 on GA media","description":"These are all security issues fixed in the cosign-2.2.4-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T02:52:41.516569Z","updated_at":"2026-11-02T16:58:36.662953Z"},{"id":"SUSE-SU-2024:1486-1","title":"Security update for cosign","description":"This update for cosign fixes the following issues:\n\n- CVE-2024-29902: Fixed denial of service on host machine via remote image with a malicious attachments (bsc#1222835)\n- CVE-2024-29903: Fixed denial of service on host machine via malicious software artifacts (bsc#1222837)\n\nOther fixes:\n- Updated to 2.2.4 (jsc#SLE-23879)\n    * Fixes for GHSA-88jx-383q-w4qc and GHSA-95pr-fxf5-86gv (#3661)\n    * ErrNoSignaturesFound should be used when there is no signature attached to an image. (#3526)\n    * fix semgrep issues for dgryski.semgrep-go ruleset (#3541)\n    * Honor creation timestamp for signatures again (#3549)\n  * Features\n    * Adds Support for Fulcio Client Credentials Flow, and Argument to Set Flow Explicitly (#3578)\n","status":"published","published":"2024-05-02T05:33:11Z","modified":"2026-02-04T03:54:05.292138Z","updated_at":"2026-11-02T15:53:54.652421Z"},{"id":"SUSE-SU-2024:1486-2","title":"Security update for cosign","description":"This update for cosign fixes the following issues:\n\n- CVE-2024-29902: Fixed denial of service on host machine via remote image with a malicious attachments (bsc#1222835)\n- CVE-2024-29903: Fixed denial of service on host machine via malicious software artifacts (bsc#1222837)\n\nOther fixes:\n- Updated to 2.2.4 (jsc#SLE-23879)\n    * Fixes for GHSA-88jx-383q-w4qc and GHSA-95pr-fxf5-86gv (#3661)\n    * ErrNoSignaturesFound should be used when there is no signature attached to an image. (#3526)\n    * fix semgrep issues for dgryski.semgrep-go ruleset (#3541)\n    * Honor creation timestamp for signatures again (#3549)\n  * Features\n    * Adds Support for Fulcio Client Credentials Flow, and Argument to Set Flow Explicitly (#3578)\n","status":"published","published":"2024-06-18T11:05:34Z","modified":"2026-02-04T03:57:15.727347Z","updated_at":"2026-11-02T15:53:54.652421Z"}]}}