CVE-2026-24137
sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal
sigstore framework is a common go library shared across sigstore services and clients. In versions 1.10.3 and below, the legacy TUF client (pkg/tuf/client.go) supports caching target files to disk. It constructs a filesystem path by joining a cache base directory with a target name sourced from signed target metadata; however, it does not validate that the resulting path stays within the cache base directory. A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has. Note that this should only affect clients that are directly using the TUF client in sigstore/sigstore or are using an older version of Cosign. Public Sigstore deployment users are unaffected, as TUF metadata is validated by a quorum of trusted collaborators. This issue has been fixed in version 1.10.4. As a workaround, users can disable disk caching for the legacy client by setting SIGSTORE_NO_CACHE=true in the environment, migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- High
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
5.8
sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal
sigstore framework is a common go library shared across sigstore services and clients. In versions 1.10.3 and below, the legacy TUF client (pkg/tuf/client.go) supports caching target files to disk. It constructs a filesystem path by joining a cache base directory with a target name sourced from signed target metadata; however, it does not validate that the resulting path stays within the cache base directory. A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has. Note that this should only affect clients that are directly using the TUF client in sigstore/sigstore or are using an older version of Cosign. Public Sigstore deployment users are unaffected, as TUF metadata is validated by a quorum of trusted collaborators. This issue has been fixed in version 1.10.4. As a workaround, users can disable disk caching for the legacy client by setting SIGSTORE_NO_CACHE=true in the environment, migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release.
- Record
CVE-2026-24137- CVSS 3.1
- 5.8 Medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
EUVDEUVD-2026-3781
5.8
sigstore framework is a common go library shared across sigstore services and clients. In versions 1.10.3 and below, the legacy TUF client (pkg/tuf/client.go) supports caching target files to disk. It constructs a filesystem path by joining a cache base directory with a target name sourced from signed target metadata; however, it does not validate that the resulting path stays within the cache base directory. A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has. Note that this should only affect clients that are directly using the TUF client in sigstore/sigstore or are using an older version of Cosign. Public Sigstore deployment users are unaffected, as TUF metadata is validated by a quorum of trusted collaborators. This issue has been fixed in version 1.10.4. As a workaround, users can disable disk caching for the legacy client by setting SIGSTORE_NO_CACHE=true in the environment, migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release.
- Record
EUVD-2026-3781- CVSS 3.1
- 5.8 Medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-fcv2-xgw5-pqxf
5.8
sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal
Summary
The legacy TUF client pkg/tuf/client.go, which supports caching target files to disk, constructs a filesystem path by joining a cache base directory with a target name sourced from signed target metadata, but it does not validate that the resulting path stays within the cache base directory.
Note that this should only affect clients that are directly using the TUF client in sigstore/sigstore or are using an older version of Cosign. As this TUF client implementation is deprecated, users should migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf as soon as possible.
Note that this does not affect users of the public Sigstore deployment, where TUF metadata is validated by a quorum of trusted collaborators.
Impact
A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has.
Workarounds
Users can disable disk caching for the legacy client by setting SIGSTORE_NO_CACHE=true in the environment, migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release.
- Record
GHSA-fcv2-xgw5-pqxf- CVSS 3.1
- 5.8 Medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
NVD
5.8
sigstore framework is a common go library shared across sigstore services and clients. In versions 1.10.3 and below, the legacy TUF client (pkg/tuf/client.go) supports caching target files to disk. It constructs a filesystem path by joining a cache base directory with a target name sourced from signed target metadata; however, it does not validate that the resulting path stays within the cache base directory. A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has. Note that this should only affect clients that are directly using the TUF client in sigstore/sigstore or are using an older version of Cosign. Public Sigstore deployment users are unaffected, as TUF metadata is validated by a quorum of trusted collaborators. This issue has been fixed in version 1.10.4. As a workaround, users can disable disk caching for the legacy client by setting SIGSTORE_NO_CACHE=true in the environment, migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release.
- Record
CVE-2026-24137- CVSS 3.1
- 5.8 Medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
OSV
5.8
sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal
sigstore framework is a common go library shared across sigstore services and clients. In versions 1.10.3 and below, the legacy TUF client (pkg/tuf/client.go) supports caching target files to disk. It constructs a filesystem path by joining a cache base directory with a target name sourced from signed target metadata; however, it does not validate that the resulting path stays within the cache base directory. A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has. Note that this should only affect clients that are directly using the TUF client in sigstore/sigstore or are using an older version of Cosign. Public Sigstore deployment users are unaffected, as TUF metadata is validated by a quorum of trusted collaborators. This issue has been fixed in version 1.10.4. As a workaround, users can disable disk caching for the legacy client by setting SIGSTORE_NO_CACHE=true in the environment, migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release.
- Record
CVE-2026-24137- CVSS 3.1
- 5.8 Medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-24137
5.8
sigstore framework is a common go library shared across sigstore services and clients. In versions 1.10.3 and below, the legacy TUF client (pkg/tuf/client.go) supports caching target files to disk. It constructs a filesystem path by joining a cache base directory with a target name sourced from signed target metadata; however, it does not validate that the resulting path stays within the cache base directory. A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has. Note that this should only affect clients that are directly using the TUF client in sigstore/sigstore or are using an older version of Cosign. Public Sigstore deployment users are unaffected, as TUF metadata is validated by a quorum of trusted collaborators. This issue has been fixed in version 1.10.4. As a workaround, users can disable disk caching for the legacy client by setting SIGSTORE_NO_CACHE=true in the environment, migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release.
- Record
DEBIAN-CVE-2026-24137- CVSS 3.1
- 5.8 Medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N - Updated
- 2026-11-02
Show 15 moreShow less
OSVGHSA-fcv2-xgw5-pqxf
5.8
sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal
Summary
The legacy TUF client pkg/tuf/client.go, which supports caching target files to disk, constructs a filesystem path by joining a cache base directory with a target name sourced from signed target metadata, but it does not validate that the resulting path stays within the cache base directory.
Note that this should only affect clients that are directly using the TUF client in sigstore/sigstore or are using an older version of Cosign. As this TUF client implementation is deprecated, users should migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf as soon as possible.
Note that this does not affect users of the public Sigstore deployment, where TUF metadata is validated by a quorum of trusted collaborators.
Impact
A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has.
Workarounds
Users can disable disk caching for the legacy client by setting SIGSTORE_NO_CACHE=true in the environment, migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release.
- Record
GHSA-fcv2-xgw5-pqxf- CVSS 3.1
- 5.8 Medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-24137
5.8
sigstore framework is a common go library shared across sigstore services and clients. In versions 1.10.3 and below, the legacy TUF client (pkg/tuf/client.go) supports caching target files to disk. It constructs a filesystem path by joining a cache base directory with a target name sourced from signed target metadata; however, it does not validate that the resulting path stays within the cache base directory. A malicious TUF repository can trigger arbitrary file overwriting, limited to the permissions that the calling process has. Note that this should only affect clients that are directly using the TUF client in sigstore/sigstore or are using an older version of Cosign. Public Sigstore deployment users are unaffected, as TUF metadata is validated by a quorum of trusted collaborators. This issue has been fixed in version 1.10.4. As a workaround, users can disable disk caching for the legacy client by setting SIGSTORE_NO_CACHE=true in the environment, migrate to https://github.com/sigstore/sigstore-go/tree/main/pkg/tuf, or upgrade to the latest sigstore/sigstore release.
- Record
UBUNTU-CVE-2026-24137- CVSS 3.1
- 5.8 Medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N - Updated
- 2026-11-02
OSVGO-2026-4358 No score
Sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal in github.com/sigstore/sigstore
Sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal in github.com/sigstore/sigstore
- Record
GO-2026-4358- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:10230-1 No score
vexctl-0.4.1+git78.f951e3a-1.1 on GA media
These are all security issues fixed in the vexctl-0.4.1+git78.f951e3a-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:10230-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:10235-1 No score
cosign-3.0.5-1.1 on GA media
These are all security issues fixed in the cosign-3.0.5-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:10235-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:10700-1 No score
apptainer-1.4.5-4.1 on GA media
These are all security issues fixed in the apptainer-1.4.5-4.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:10700-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:20386-1 No score
Security update for cosign
This update for cosign fixes the following issues:
Update to version 3.0.5:
- CVE-2026-24122: Fixed improper validation of certificates that outlive expired CA certificates (bsc#1258542)
- CVE-2026-26958: Fixed filippo.io/edwards25519: failure to initialize receiver in MultiScalarMult can produce invalid results and lead to undefined behavior (bsc#1258612)
- CVE-2026-24137: Fixed github.com/sigstore/sigstore/pkg/tuf: legacy TUF client allows for arbitrary file writes with target cache path traversal (bsc#1257139)
- CVE-2026-22772: Fixed github.com/sigstore/fulcio: bypass MetaIssuer URL validation bypass can trigger SSRF to arbitrary internal services (bsc#1256562)
- CVE-2026-23991: Fixed github.com/theupdateframework/go-tuf/v2: denial of service due to invalid TUF metadata JSON returned by TUF repository (bsc#1257080)
- CVE-2026-23992: Fixed github.com/theupdateframework/go-tuf/v2: unauthorized modification to TUF metadata files due to a compromised or misconfigured TUF repository (bsc#1257085)
- CVE-2025-11065: Fixed github.com/go-viper/mapstructure/v2: sensitive Information leak in logs (bsc#1250620)
- CVE-2026-22703: Fixed that cosign verification accepts any valid Rekor entry under certain conditions (bsc#1256496)
- CVE-2025-58181: Fixed golang.org/x/crypto/ssh: invalidated number of mechanisms can cause unbounded memory consumption (bsc#1253913)
- Record
openSUSE-SU-2026:20386-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:20730-1 No score
Security update for apptainer
This update for apptainer fixes the following issues:
Changes in apptainer:
-
Fix CVE-2026-34986 (bsc#1262956) * github.com/go-jose/go-jose/[email protected] CVE-2026-33186 GO-2026-4762 (bsc#1260311) * google.golang.org/[email protected] CVE-2026-24137 GO-2026-4358 (bsc#1264177) * github.com/sigstore/[email protected] Fix fallout: github.com/moby/[email protected] github.com/containers/image/v5=github.com/containers/image/[email protected]
-
Fix HTML parser misimplementation of a part of the HTML specification for table related tags (CVE-2025-58190, GO-2026-4441, bsc#1258048).
-
Fix issue where the HTML parser takes a very long time or even never returns (CVE-2025-47911, GO-2026-4440, bsc#1258047).
-
Update ot 1.4.5
- Fix for moderate severity GO-2025-4176 / CVE-2025-65105 / GHSA-j3rw-fx6g-q46j (bsc#1255462): Ineffective application of selinux / apparmor --security option. Updates of a few dependent go libraries for related security fixes.
- Other fix Run FUSE processes in a separate process group. This detaches them from the main process so they don't receive signals such as interrupts sent to a terminal there. This was not a problem with interactive shells because they start their own group, but was a problem with some programs with interactive Read/Eval/Print/Loops such as python. An interrupt there would kill the FUSE processes.
-
From 1.4.4
- By applying patches to the bundled fuse2fs, allow again the possibility of using a non-writable ext3 image file as an overlay. Fixes regression introduced in 1.4.3.
- If an overlay or bound data image is asked to be mounted writable but the user has no write access to the image, show a warning message instead of silently switching to readonly.
- Avoid a fatal error when starting fakeroot from suid mode while in an NFS directory.
- Fix 32-bit builds which were accidentally broken by a library upgrade that was done for a minor security issue.
-
Fix CVEs:
- GO-2025-4135 - CVE-2025-47914 Malformed constraint may cause denial of service in golang.org/x/crypto/ssh/agent.
- GO-2025-4134 - CVE-2025-58181 - bsc#1253924 Unbounded memory consumption in golang.org/x/crypto/ssh.
- GO-2025-4116 - CVE-2025-47913 Potential denial of service in golang.org/x/crypto/ssh/agent.
- GO-2025-3595 - CVE-2025-22872 Incorrect Neutralization of Input During Web Page Generation in x/net.
- GO-2025-3503 - CVE-2025-22870 HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net.
- GO-2025-3487 - CVE-2025-22869 Potential denial of service in golang.org/x/crypto.
- GO-2025-3485 - CVE-2025-27144 DoS in go-jose Parsing in github.com/go-jose/go-jose.
- GO-2025-3754 - CVE-2025-8556 CIRCL-Fourq: Missing and wrong validation can lead to incorrect results in github.com/cloudflare/circl.
-
No need for binutils-gold for aarch64
-
Update to 1.4.3
- Corrected the mconfig -s option for statically building apptainer and starter binaries.
- Resolved an issue where the Makefile generated by mconfig -b failed when the build directory was not a subdirectory of the Apptainer source code.
- Fixed %files in definition files to correctly copy symlinks pointing above the destination directory but within the destination stage root filesystem.
- Addressed a typo in nvliblist.conf ( libnvoptix.so.1 was corrected to libnvoptix.so).
- Prevented timeouts during cleanup after building gocryptfs-encrypted SIF files.
- Fixed a bug that prevented build with --passphrase or --pem-path (without --encrypt) from implying fakeroot.
- Resolved a hang when copying files between build stages while using suid mode without user namespaces.
- Fixed issues with running and building containers of different architectures than the host via binfmt_misc when using rootless fakeroot.
- Corrected "target: no such file or directory" errors when …
- Record
openSUSE-SU-2026:20730-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21481-1 No score
Security update for vexctl
This update for vexctl fixes the following issues:
- CVE-2024-45337: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto (bsc#1234486).
- CVE-2025-22868: golang.org/x/oauth2/jws: Unexpected memory consumption during token parsing in golang.org/x/oauth2 (bsc#1239186).
- CVE-2025-22869: golang.org/x/crypto/ssh: Denial of Service in the Key Exchange of golang.org/x/crypto/ssh (bsc#1239323).
- CVE-2025-22870: golang.org/x/net/proxy: proxy bypass using IPv6 zone IDs (bsc#1238683).
- CVE-2025-27144: github.com/go-jose/go-jose/v4,github.com/go-jose/go-jose/v3: Go JOSE's Parsing Vulnerable to Denial of Service (bsc#1237611).
- CVE-2025-30204: github.com/golang-jwt/jwt/v4: jwt-go allows excessive memory allocation during header parsing (bsc#1240444).
- CVE-2025-58181: golang.org/x/crypto/ssh: invalidated number of mechanisms can cause unbounded memory consumption (bsc#1253802).
- CVE-2026-22772: github.com/sigstore/fulcio: bypass MetaIssuer URL validation bypass can trigger SSRF to arbitrary internal services (bsc#1256535).
- CVE-2026-24137: github.com/sigstore/sigstore/pkg/tuf: legacy TUF client allows for arbitrary file writes with target cache path traversal (bsc#1257138).
Changes for vexctl:
- Update to version 0.4.4+git20.5d61136:
- build(deps): Bump github.com/sigstore/cosign/v2
- build(deps): Bump actions/setup-go from 6.5.0 to 7.0.0
- build(deps): Bump the all group across 1 directory with 5 updates
- build(deps): Bump github.com/sigstore/rekor in the all group
- build(deps): Bump the all group with 4 updates
- build(deps): Bump github.com/google/go-containerregistry
- build(deps): Bump actions/setup-go from 6.4.0 to 6.5.0 in the all group
- build(deps): Bump the all group across 1 directory with 2 updates
- build(deps): Bump actions/checkout from 6.0.3 to 7.0.0
- build(deps): Bump chainguard-dev/actions in the all group
- Update to version 0.4.4:
- fix signature duplication
- fix lints
- housekeeping - deps update and ci cleanup
- build(deps): Bump the all group with 2 updates
- build(deps): Bump github.com/sigstore/sigstore in the all group
- build(deps): Bump golangci/golangci-lint-action in the all group
- Update to version 0.4.1+git147.b7e6ef0:
- build(deps): Bump goreleaser/goreleaser-action in the all group
- Bump sigstore/cosign-installer from 4.1.1 to 4.1.2 in the all group
- Bump chainguard-dev/actions from 1.6.17 to 1.6.19 in the all group
- Bump chainguard-dev/actions from 1.6.16 to 1.6.17 in the all group
- Bump github.com/package-url/packageurl-go in the all group
- Bump the all group with 2 updates
- Update to version 0.4.1+git133.efecaf7:
- Bump github.com/secure-systems-lab/go-securesystemslib
- Update to version 0.4.1+git129.c7f3066:
- Bump github.com/google/go-containerregistry in the all group
- Bump github.com/sigstore/timestamp-authority/v2 from 2.0.3 to 2.0.6
- Bump softprops/action-gh-release from 2.6.1 to 3.0.0
- Bump chainguard-dev/actions from 1.6.13 to 1.6.14 in the all group
- Bump actions/upload-artifact from 7.0.0 to 7.0.1 in the all group
- Bump github.com/sigstore/cosign/v2 from 2.6.2 to 2.6.3 in the all group
- Bump kubernetes-sigs/release-actions in the all group
- Bump github.com/in-toto/in-toto-golang from 0.9.0 to 0.10.0
- Bump the all group across 1 directory with 2 updates
- Bump github.com/go-jose/go-jose/v4 from 4.1.3 to 4.1.4
- fix(add): allow add without --product flag
- Use gomod version, bump linter
- Port vexctl to intoto/attestation
- Bump the all group across 1 directory with 5 updates
- Bump google.golang.org/grpc from 1.78.0 to 1.79.3
- Update to version 0.4.1+git96.558125d:
- Bump the all group across 1 directory with 3 updates
- Bump chainguard-dev/actions from 1.6.5 to 1.6.6 in the all group
- Bump github.com/google/go-containerregistry from 0.20.7 to 0.21.0
- Bump actions/upload-artifact from 6.0.0 to 7.0.0
- Bump…
- Record
openSUSE-SU-2026:21481-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21483-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260723T184607 2026-07-23T18:46:07Z (jsc#PED-11136).
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-4730 CVE-2026-33022 GHSA-cv4x-93xx-wgfj
- GO-2026-4761 CVE-2026-33211 GHSA-j5q5-j9gm-2w5c
- GO-2026-5102 CVE-2026-45021 GHSA-3vcp-chfh-f6r2
- GO-2026-5272 CVE-2026-40938 GHSA-94jr-7pqp-xhcq
- GO-2026-5486 CVE-2026-40924 GHSA-m2cx-gpqf-qf74
- GO-2026-5542 CVE-2026-40090 GHSA-pj97-4p9w-gx3q
- GO-2026-5630 CVE-2026-25542 GHSA-rmx9-2pp3-xhcr
- GO-2026-5643 CVE-2026-40923 GHSA-rx35-6rhx-7858
- GO-2026-5675 CVE-2026-41492 GHSA-vvf7-6rmr-m29q
- GO-2026-5711 CVE-2026-40161 GHSA-wjxp-xrpv-xpff
- GO-2026-5746 CVE-2026-41567 GHSA-x86f-5xw2-fm2r
- GO-2026-5749 CVE-2026-41328 GHSA-x92x-px7w-4gx4
- GO-2026-5837 CVE-2026-44840 GHSA-q2m9-6jp9-c6mc
- GO-2026-5929 CVE-2026-44342 GHSA-26v7-h57m-gh9m
- GO-2026-5930 CVE-2026-33655 GHSA-6qcr-qxgr-m7fv
- GO-2026-5933 GHSA-3g4q-2f67-2gvh
- GO-2026-5934 GHSA-59qp-cfj3-rp64
- GO-2026-5935 GHSA-7856-g3gv-9wq8
- GO-2026-5936 CVE-2026-53552 GHSA-26rh-24rg-j3vv
- GO-2026-5937 CVE-2026-53508 GHSA-2jcc-mxv7-p3f9
- GO-2026-5938 CVE-2026-53553 GHSA-4g5x-hcwm-82jw
- GO-2026-5939 CVE-2026-10517 GHSA-698x-9w2p-7vvp
- GO-2026-5940 CVE-2026-53572 GHSA-6w3m-4hhp-775q
- GO-2026-5941 CVE-2026-53487 GHSA-gvhc-wv3v-7pf8
- GO-2026-5942 CVE-2026-46600
- GO-2026-5944 CVE-2026-50197 GHSA-659f-rgp5-w4wf
- GO-2026-5945 CVE-2026-6815 GHSA-rmxx-v9rj-vpvg
- GO-2026-5946 CVE-2026-52831 GHSA-v5px-423j-pf7p
- GO-2026-5947 CVE-2026-53649 GHSA-xqhv-chqm-fhcc
- GO-2026-5948 CVE-2026-50554 GHSA-588f-fvcv-xhvf
- GO-2026-5949 CVE-2026-50553 GHSA-rqrh-8wpv-x7hh
- GO-2026-5950 CVE-2026-53602 GHSA-339v-266x-79xr
- GO-2026-5951 CVE-2026-10219 GHSA-6jm8-4fhr-5w64
- GO-2026-5952 CVE-2026-49834 GHSA-9vcr-p3rj-q5q6
- GO-2026-5953 CVE-2026-9094 GHSA-c9w5-qp6m-m395
- GO-2026-5956 CVE-2026-55252 GHSA-h5g6-xmh4-hc37
- GO-2026-5957 CVE-2026-54158 GHSA-5xfx-xj4h-5p7r
- GO-2026-5958 CVE-2026-54068 GHSA-gcm7-57gf-953c
- GO-2026-5959 CVE-2026-54072 GHSA-h29v-hj44-q8cv
- GO-2026-5961 CVE-2026-54069 GHSA-hvr9-72v2-fff3
- GO-2026-5962 CVE-2026-54088 GHSA-m93h-4hw7-5qcm
- GO-2026-5963 CVE-2026-54067 GHSA-mvjr-vv3c-w4qv
- GO-2026-5964 CVE-2026-54066 GHSA-p4m3-mgmm-c664
- GO-2026-5965 CVE-2026-54070 GHSA-w7cg-whh7-xp28
- GO-2026-5966 CVE-2026-54089 GHSA-xqp3-jq6g-x3qm
- GO-2026-5967 CVE-2026-50551 GHSA-56mp-4f3v-fgj2
- GO-2026-5968 CVE-2026-54174 GHSA-fpg8-7664-jc5q
- GO-2026-5969 GHSA-g936-7jqj-mwv8
- GO-2026-5970 CVE-2026-56852
- GO-2026-5973 CVE-2026-54250 GHSA-jxr7-mqhw-9p98
- GO-2026-5974 CVE-2026-44300 GHSA-wmj8-9953-vff5
- GO-2026-5975 CVE-2026-50018 GHSA-42j2-w334-qxw7
- GO-2026-5976 CVE-2026-50141 GHSA-g7mm-9vx7-jm7h
- GO-2026-5977 CVE-2026-50013 GHSA-qrh4-p6v4-mrfg
- GO-2026-5978 CVE-2026-50125 GHSA-qw5r-ppcg-f8rj
- GO-2026-5979 CVE-2026-50006 GHSA-xrcf-6jh3-ggvx
- GO-2026-5980 CVE-2026-50158 GHSA-2c7f-fxww-6w6c
- GO-2026-5981 GHSA-mqxv-9rm6-w8qc
- GO-2026-5982 GHSA-pqg7-v6wh-3pfp
- GO-2026-5984 CVE-2026-53604 GHSA-2p2f-px33-4vv5
- GO-2026-5985 GHSA-7rx3-5wx3-5v76
- GO-2026-5986 CVE-2026-61699 GHSA-cm26-5974-52h8
- GO-2026-5987 CVE-2026-55513 GHSA-g4x6-jcvr-9m3g
- GO-2026-5988 CVE-2026-54628 GHSA-hwrq-8wxh-q4xv
- GO-2026-5989 CVE-2026-55512 GHSA-m3cx-mwpg-32jg
- GO-2026-5990 CVE-2026-54629 GHSA-mf78-3rpf-r784
- GO-2026-5991 CVE-2026-53603 GHSA-q4vm-pq3q-8wgq
- GO-2026-5992 CVE-2026-61549 GHSA-qf34-295c-26v8
- GO-2026-5996 CVE-2026-54450 GHSA-pph6-vfjv-vpjw
- GO-2026-5997 CVE-2026-54452 GHSA-xgch-x3mx-cm3c
- GO-2026-5998 CVE-2026-54495 GHSA-398h-7f66-3h4p
- GO-2026-5999 CVE-2026-10814 GHSA-jh6h-v6mp-h22v
- GO-2026-6002 CVE-2026-58196 GHSA-pr64-jmmf-jp54
- GO-2026-6003 CVE-2026-53714 GHSA-22xc-xg2r-9j7v
- GO-2026-6004 CVE-2026-52833 GHSA-3v79-m2cg-89ww
- GO-2026-6005 CVE-2026-53715 GHSA-8fv2-88gg-hm7q
- GO-2026-6006 CVE-2026-53716 GHSA-cxpq-8v7q-cg56 *…
- Record
openSUSE-SU-2026:21483-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:0592-1 No score
Security update for vexctl
This update for vexctl fixes the following issues:
- Update to version 0.4.1+git78.f951e3a:
- CVE-2025-22868: Unexpected memory consumption during token parsing in golang.org/x/oauth2. (bsc#1239186)
- CVE-2024-45337: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto. (bsc#1234486)
- CVE-2025-27144: Go JOSE's Parsing Vulnerable to Denial of Service. (bsc#1237611)
- CVE-2025-22870: proxy bypass using IPv6 zone IDs. (bsc#1238683)
- CVE-2025-22869: Denial of Service in the Key Exchange of golang.org/x/crypto/ssh. (bsc#1239323)
- CVE-2025-30204: jwt-go allows excessive memory allocation during header parsing. (bsc#1240444)
- CVE-2025-58181: invalidated number of mechanisms can cause unbounded memory consumption. (bsc#1253802)
- CVE-2026-22772: MetaIssuer URL validation bypass can trigger SSRF to arbitrary internal services. (bsc#1256535)
- CVE-2026-24137: legacy TUF client allows for arbitrary file writes with target cache path traversal. (bsc#1257138)
- Record
SUSE-SU-2026:0592-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:0757-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
Update to version 0.0.20260226T182644 2026-02-26T18:26:44Z (jsc#PED-11136) Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2025-4259 CVE-2025-13767 GHSA-fmqf-pmcm-8cx9
- GO-2025-4260 CVE-2025-64641 GHSA-vww6-79rv-3j4x
- GO-2026-4282 CVE-2017-18873 GHSA-x6mw-hf2j-vqpc
- GO-2026-4305 CVE-2017-18903 GHSA-fcwg-45jh-5qhf
- GO-2026-4325 CVE-2025-14822 GHSA-9r42-rhw3-2222
- GO-2026-4326 CVE-2025-14435 GHSA-mx8m-v8qm-xwr8
- GO-2026-4332 CVE-2026-23644 GHSA-2657-3c98-63jq
- GO-2026-4348 CVE-2026-23991 GHSA-846p-jg2w-w324
- GO-2026-4349 CVE-2026-23992 GHSA-fphv-w9fq-2525
- GO-2026-4377 CVE-2026-24686 GHSA-jqc5-w2xx-5vq4
- GO-2026-4410 CVE-2026-25140 GHSA-f4w5-5xv9-85f6
- GO-2026-4502 CVE-2026-25766 GHSA-pgvm-wxw2-hrv9
- GO-2026-4534 CVE-2026-25899 GHSA-2mr3-m5q5-wgp6
- GO-2026-4535 CVE-2026-27585 GHSA-4xrr-hq4w-6vf4
- GO-2026-4536 CVE-2026-27590 GHSA-5r3v-vc8m-m96g
- GO-2026-4537 CVE-2026-27589 GHSA-879p-475x-rqh2
- GO-2026-4538 CVE-2026-27587 GHSA-g7pc-pc7g-h8jh
- GO-2026-4539 CVE-2026-27586 GHSA-hffm-g8v7-wrv7
- GO-2026-4540 CVE-2026-25891 GHSA-m3c2-496v-cw3v
- GO-2026-4541 CVE-2026-27588 GHSA-x76f-jf84-rqj8
- GO-2026-4543 CVE-2026-25882 GHSA-mrq8-rjmw-wpq3
- GO-2026-4559 CVE-2026-27141
Update to version 0.0.20260225T230704 2026-02-25T23:07:04Z.
- GO-2026-4358 CVE-2026-24137 GHSA-fcv2-xgw5-pqxf
- GO-2026-4361 GHSA-c32p-wcqj-j677
- GO-2026-4394 CVE-2026-24051 GHSA-9h8m-3fm2-qjrq
- GO-2026-4399 CVE-2026-25518 GHSA-gx3x-vq4p-mhhv
- GO-2026-4507 CVE-2026-26314 GHSA-2gjw-fg97-vg3r
- GO-2026-4508 CVE-2026-26313 GHSA-689v-6xwf-5jf3
- GO-2026-4509 CVE-2026-27017 GHSA-7m29-f4hw-g2vx
- GO-2026-4511 CVE-2026-26315 GHSA-m6j8-rg6r-7mv8
- GO-2026-4512 CVE-2026-26995 GHSA-rrxv-pmq9-x67r
- GO-2026-4531 CVE-2026-25591 GHSA-w6x6-9fp7-fqm4
- GO-2026-4532 CVE-2026-25802 GHSA-299v-8pq9-5gjq
- GO-2026-4533 CVE-2026-27571 GHSA-qrvq-68c2-7grw
- GO-2026-4542 CVE-2026-27598 GHSA-6v48-fcq6-ff23
- GO-2026-4545 CVE-2025-50180 GHSA-3c9r-837r-qqm4
- GO-2026-4546 CVE-2026-27611 GHSA-8vrh-3pm2-v4v6
- GO-2026-4547 CVE-2026-27626 GHSA-49gm-hh7w-wfvf
- GO-2026-4548 GHSA-2phg-qgmm-r638
Update to version 0.0.20260223T182315 2026-02-23T18:23:15Z.
- GO-2026-4392 CVE-2026-24845 GHSA-9m43-p3cx-w8j5
- GO-2026-4434 CVE-2023-43635 GHSA-4jvr-vj2c-8q37
- GO-2026-4435 CVE-2023-43636 GHSA-5h7v-g49c-h887
- GO-2026-4436 CVE-2023-43637 GHSA-g7vp-j25f-h34p
- GO-2026-4442 GHSA-x9p2-77v6-6vhf
- GO-2026-4444 CVE-2026-23989 GHSA-9j2f-3rj3-wgpg
- GO-2026-4445 CVE-2026-25760 GHSA-2286-hxv5-cmp2
- GO-2026-4446 CVE-2026-24851 GHSA-jq9f-gm9w-rwm9
- GO-2026-4447 GHSA-vf5j-r2hw-2hrw
- GO-2026-4448 CVE-2025-64111 GHSA-gg64-xxr9-qhjp
- GO-2026-4449 CVE-2025-64175 GHSA-p6x6-9mx6-26wj
- GO-2026-4450 CVE-2026-23632 GHSA-5qhx-gwfj-6jqr
- GO-2026-4451 CVE-2026-22592 GHSA-cr88-6mqm-4g57
- GO-2026-4452 CVE-2026-24135 GHSA-jp7c-wj6q-3qf2
- GO-2026-4453 CVE-2026-23633 GHSA-mrph-w4hh-gx3g
- GO-2026-4454 GHSA-26gq-grmh-6xm6
- GO-2026-4455 CVE-2025-70963 GHSA-9f8m-9547-2gqm
- GO-2026-4456 CVE-2025-13523 GHSA-ffx7-34p2-vm3w
- GO-2026-4457 CVE-2025-65852 GHSA-rjv5-9px2-fqw6
- GO-2026-4458 CVE-2026-25793 GHSA-69x3-g4r3-p962
- GO-2026-4459 CVE-2017-18907 GHSA-42x9-rr3c-gr59
- GO-2026-4460 CVE-2017-18918 GHSA-5ghq-28r7-qwfj
- GO-2026-4461 CVE-2026-25804 GHSA-86x4-wp9f-wrr9
- GO-2026-4462 CVE-2017-18915 GHSA-hxxj-8phw-74vw
- GO-2026-4463 CVE-2017-18917 GHSA-jxc4-w54c-qv5r
- GO-2026-4464 CVE-2017-18911 GHSA-m462-mqw4-2c8m
- GO-2026-4465 GHSA-vhvq-fv9f-wh4q
- GO-2026-4466 CVE-2026-25791 GHSA-wxrw-gvg8-fqjp
- GO-2026-4467 CVE-2017-18916 GHSA-x33g-375j-jhf7
- GO-2026-4471 CVE-2025-66630 GHSA-68rr-p4fp-j59v
- GO-2026-4473 CVE-2026-25934 GHSA-37cx-329c-33x3
- GO-2026-4474 CVE-2026-25890 GHSA-4mh3-h929-w968
- GO-2026-4475 CVE-2026-25889 GHSA-hxw8-4h9j-hq2r
- GO-2026-4476 CVE-2017-18908…
- Record
SUSE-SU-2026:0757-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:0777-1 No score
Security update for cosign
This update for cosign fixes the following issues:
Update to version 3.0.5 (jsc#SLE-23879).
Security issues fixed:
- CVE-2025-11065: github.com/go-viper/mapstructure/v2: sensitive Information leak in logs (bsc#1250620).
- CVE-2025-58181: golang.org/x/crypto/ssh: invalidated number of mechanisms can cause unbounded memory consumption (bsc#1253913).
- CVE-2026-22703: Verification accepts any valid Rekor entry under certain conditions (bsc#1256496).
- CVE-2026-22772: github.com/sigstore/fulcio: bypass MetaIssuer URL validation bypass can trigger SSRF to arbitrary internal services (bsc#1256562).
- CVE-2026-23991: github.com/theupdateframework/go-tuf/v2: denial of service due to invalid TUF metadata JSON returned by TUF repository (bsc#1257080).
- CVE-2026-23992: github.com/theupdateframework/go-tuf/v2: unauthorized modification to TUF metadata files due to a compromised or misconfigured TUF repository (bsc#1257085).
- CVE-2026-24122: improper validation of certificates that outlive expired CA certificates (bsc#1258542).
- CVE-2026-24137: github.com/sigstore/sigstore/pkg/tuf: legacy TUF client allows for arbitrary file writes with target cache path traversal (bsc#1257139).
- CVE-2026-26958: filippo.io/edwards25519: failure to initialize receiver in MultiScalarMult can produce invalid results and lead to undefined behavior (bsc#1258612).
Other updates and bugfixes:
- chore(deps): bump google.golang.org/api from 0.260.0 to 0.264.0 (#4679)
- chore(deps): bump github.com/sigstore/rekor-tiles/v2 from 2.0.1 to 2.1.0 (#4670)
- chore(deps): bump filippo.io/edwards25519 from 1.1.0 to 1.1.1 (#4712)
- chore(deps): bump gitlab.com/gitlab-org/api/client-go (#4680)
- chore(deps): bump the gomod group across 1 directory with 4 updates (#4702)
- chore(deps): bump the actions group with 3 updates (#4703)
- update golang builder to use go1.25.7 (#4687)
- update golangci-lint to v2.8.x (#4688)
- Support DSSE signing conformance test (#4685)
- chore(deps): bump the actions group across 1 directory with 8 updates (#4689)
- Deprecate rekor-entry-type flag (#4691)
- Deprecate cosign triangulate (#4676)
- Deprecate cosign copy (#4681)
- Enforce TSA requirement for Rekor v2, Fuclio signing (#4683)
- chore(deps): bump github.com/theupdateframework/go-tuf/v2 (#4668)
- chore(deps): bump golang from 1.25.5 to 1.25.6 in the all group (#4673)
- Automatically require signed timestamp with Rekor v2 entries (#4666)
- Fix syntax issue in conformance test, update nightly (#4664)
- Add mTLS support for TSA client connections when signing with a signing config (#4620)
- fix: avoid panic on malformed tlog entry body (#4652)
- Verify validity of chain rather than just certificate (#4663)
- Allow --local-image with --new-bundle-format for v2 and v3 signatures (#4626)
- chore(deps): bump the gomod group across 1 directory with 3 updates (#4662)
- Bump sigstore/sigstore to resolve GHSA (#4660)
- Gracefully fail if bundle payload body is not a string (#4648)
- fix: avoid panic on malformed replace payload (#4653)
- chore(deps): bump github.com/sigstore/rekor from 1.4.3 to 1.5.0 (#4659)
- fix: avoid panic on malformed attestation payload (#4651)
- fix: avoid panic on malformed tlog entries (#4649)
- Update conformance to latest
- docs(cosign): clarify RFC3161 revocation semantics (#4642)
- Add empty predicate to cosign sign when payload type is application/vnd.in-toto+json (#4635)
- chore(deps): bump github.com/sigstore/fulcio from 1.8.4 to 1.8.5 (#4637)
- Add origin key for ctfe trusted root
- Add changelog updates for v3.0.4 and v2.6.2 (#4625)
- Update to version 3.0.4:
- Fix bundle verify path for old bundle/trusted root (#4623)
- chore(deps): bump gitlab.com/gitlab-org/api/client-go (#4616)
- chore(deps): bump cuelang.org/go in the gomod group (#4615)
- Optimize cosign tree performance by caching digest resolution (#4612)
- Don't require a trusted root to verify offline with a key (#4613)
- Support default services for trusted-root and…
- Record
SUSE-SU-2026:0777-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:20904-1 No score
Security update for cosign
This update for cosign fixes the following issues:
Update to version 3.0.5:
- CVE-2026-24122: Fixed improper validation of certificates that outlive expired CA certificates (bsc#1258542)
- CVE-2026-26958: Fixed filippo.io/edwards25519: failure to initialize receiver in MultiScalarMult can produce invalid results and lead to undefined behavior (bsc#1258612)
- CVE-2026-24137: Fixed github.com/sigstore/sigstore/pkg/tuf: legacy TUF client allows for arbitrary file writes with target cache path traversal (bsc#1257139)
- CVE-2026-22772: Fixed github.com/sigstore/fulcio: bypass MetaIssuer URL validation bypass can trigger SSRF to arbitrary internal services (bsc#1256562)
- CVE-2026-23991: Fixed github.com/theupdateframework/go-tuf/v2: denial of service due to invalid TUF metadata JSON returned by TUF repository (bsc#1257080)
- CVE-2026-23992: Fixed github.com/theupdateframework/go-tuf/v2: unauthorized modification to TUF metadata files due to a compromised or misconfigured TUF repository (bsc#1257085)
- CVE-2025-11065: Fixed github.com/go-viper/mapstructure/v2: sensitive Information leak in logs (bsc#1250620)
- CVE-2026-22703: Fixed that cosign verification accepts any valid Rekor entry under certain conditions (bsc#1256496)
- CVE-2025-58181: Fixed golang.org/x/crypto/ssh: invalidated number of mechanisms can cause unbounded memory consumption (bsc#1253913)
- Record
SUSE-SU-2026:20904-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:2609-1 No score
Security update for apptainer
This update for apptainer fixes the following issues
- CVE-2026-24137: github.com/sigstore/sigstore/pkg/tuf: legacy TUF client allows for arbitrary file writes with target cache path traversal (bsc#1264177).
- CVE-2026-33186: google.golang.org/grpc: authorization bypass due to improper validation of the HTTP/2: path pseudo- header (bsc#1260311).
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265844).
- CVE-2026-34986: github.com/go-jose/go-jose/v4,github.com/go-jose/go-jose/v3: crafted JWE input with a missing encrypted key can lead to a denial of service (bsc#1262956).
- CVE-2026-39821: golang.org/x/net/idna: failure to reject ASCII-only Punycode-encoded labels allows for validation bypass and privilege escalation (bsc#1266656).
- CVE-2026-39827: memory leak when rejecting channels can lead to DoS in golang.org/x/crypto/ssh (bsc#1266202).
- CVE-2026-39828: bypass of certificate restrictions in golang.org/x/crypto/ssh (bsc#1266202).
- CVE-2026-39829: pathological RSA/DSA parameters may cause DoS in golang.org/x/crypto/ssh (bsc#1266202).
- CVE-2026-39830: client can cause server deadlock on unexpected responses in golang.org/x/crypto/ssh (bsc#1266202).
- CVE-2026-39831: bypass of FIDO/U2F security keys physical interaction in golang.org/x/crypto/ssh (bsc#1266202).
- CVE-2026-39832: agent constraints dropped when forwarding keys in golang.org/x/crypto/ssh/agent (bsc#1266202).
- CVE-2026-39833: key constraints not enforced in golang.org/x/crypto/ssh/agent (bsc#1266202).
- CVE-2026-39834: infinite loop on large channel writes in golang.org/x/crypto/ssh (bsc#1266202).
- CVE-2026-39835: server panic during CheckHostKey/Authenticate in golang.org/x/crypto/ssh (bsc#1266202).
- CVE-2026-42508: auth bypass via unenforced @revoked status in golang.org/x/crypto/ssh/knownhosts (bsc#1266202).
- CVE-2026-46595: VerifiedPublicKeyCallback permissions skip enforcement in golang.org/x/crypto/ssh (bsc#1266202).
- CVE-2026-46597: byte arithmetic causes underflow and panic in golang.org/x/crypto/ssh (bsc#1266202).
- CVE-2026-46598: pathological inputs can lead to client panic in golang.org/x/crypto/ssh/agent (bsc#1266202).
- CVE-2026-48785: incorrect path matching for limit container paths directive (bsc#1267982).
Changes for apptainer:
- Update apptainer to version v1.5.1
- Work around segmentation fault sometimes seen while
mksquashfsunder proot is creating a SIF file. - Update bundled PRoot to version 5.4.0-rootless.3 in order to
fix a problem where SIF files could be corrupted when
mksquashfsdied with a signal. The proot command was not passing back an error exit code. - Updated bundled
squashfuse_llto version 0.6.2 in order to fix a crash sometimes seen with apptainer in unprivileged docker. - Update bundled fuse2fs to version 1.47.4 instead of patching the bugs in 1.47.3.
- Fix a crash that happened when
/etc/resolv.confwas a symlink while building from a definition file using the localimage bootstrap. - Support hosts that have an /etc/resolv.conf symlink pointing
to
../runin addition to/run. - Change the download-dependencies script to skip downloading the PRoot source code on architectures that it is known to not support (that is: ppc*, s390*, and riscv*). In those situations Apptainer will skip trying to compile and run proot. As a result original owners and groups of files will not be preserved in SIF images built by unprivileged users, as was the case for all architectures prior to 1.5.0.
- Fix panic encountered during progress bar update while pulling image.
- Fix fakeroot overwriting root's username in
/etc/passwdwith the host user's name, a regression introduced in v1.5.0. - Add nonested flag for --mount specifications to prevent
individual bind mounts from being passed to nested containers
via
APPTAINER_BIND.
- Record
SUSE-SU-2026:2609-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/sigstore/sigstoreGo |
through 1.10.3 | 1.10.4 |
golang-github-sigstore-sigstoreDebian:13 |
All versions, plus listed versions 1.10.1-11.10.3-11.10.4-11.10.5-11.10.6-1 Show 4 moreShow less1.10.8-11.10.9-11.9.3-21.9.5-1 |
None known |
golang-github-sigstore-sigstoreDebian:14 |
before 1.10.4-1, plus listed versions 1.10.1-11.10.3-11.9.3-21.9.5-1 |
1.10.4-1 |
github.com/sigstore/sigstoreGo |
before 1.10.4 | 1.10.4 |
vexctlopenSUSE:Leap 15.6 From an advisory covering 9 CVEs |
before 0.4.1+git78.f951e3a-150000.1.11.1 | 0.4.1+git78.f951e3a-150000.1.11.1 |
govulncheck-vulndbopenSUSE:Leap 15.6 From an advisory covering 104 CVEs |
before 0.0.20260226T182644-150000.1.149.1 | 0.0.20260226T182644-150000.1.149.1 |
cosignSUSE:Linux Enterprise Module for Basesystem 15 SP7 From an advisory covering 9 CVEs |
before 3.0.5-150400.3.35.1 | 3.0.5-150400.3.35.1 |
cosignopenSUSE:Leap 15.6 From an advisory covering 9 CVEs |
before 3.0.5-150400.3.35.1 | 3.0.5-150400.3.35.1 |
cosignSUSE:Linux Enterprise Server 16.0 From an advisory covering 9 CVEs |
before 3.0.5-160000.1.1 | 3.0.5-160000.1.1 |
cosignSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 9 CVEs |
before 3.0.5-160000.1.1 | 3.0.5-160000.1.1 |
Show 12 moreShow less
| Package | Affected | Fixed |
|---|---|---|
apptainerSUSE:Linux Enterprise Module for HPC 15 SP7 From an advisory covering 19 CVEs |
before 1.5.1-150600.4.24.1 | 1.5.1-150600.4.24.1 |
apptainerSUSE:Linux Enterprise Server 15 SP6-LTSS From an advisory covering 19 CVEs |
before 1.5.1-150600.4.24.1 | 1.5.1-150600.4.24.1 |
golang-github-sigstore-sigstoreUbuntu:24.04:LTS |
All versions, plus listed versions 1.4.0-31.7.5-11.8.0-2 |
None known |
golang-github-sigstore-sigstoreUbuntu:25.10 |
All versions, plus listed versions 1.8.12-11.9.3-2 |
None known |
golang-github-sigstore-sigstoreUbuntu:26.10 |
All versions, plus listed versions 1.10.4-11.10.9-1 |
None known |
golang-github-sigstore-sigstoreUbuntu:26.04:LTS |
All versions, plus listed versions 1.9.3-21.9.5-11.10.1-11.10.3-11.10.4-1 |
None known |
vexctlopenSUSE:Tumbleweed From an advisory covering 9 CVEs |
before 0.4.1+git78.f951e3a-1.1 | 0.4.1+git78.f951e3a-1.1 |
cosignopenSUSE:Tumbleweed From an advisory covering 6 CVEs |
before 3.0.5-1.1 | 3.0.5-1.1 |
apptaineropenSUSE:Tumbleweed From an advisory covering 3 CVEs |
before 1.4.5-4.1 | 1.4.5-4.1 |
cosignopenSUSE:Leap 16.0 From an advisory covering 9 CVEs |
before 3.0.5-160000.1.1 | 3.0.5-160000.1.1 |
vexctlopenSUSE:Leap 16.0 From an advisory covering 9 CVEs |
before 0.4.4+git20.5d61136-160000.1.1 | 0.4.4+git20.5d61136-160000.1.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 1734 CVEs |
before 0.0.20260723T184607-160000.1.1 | 0.0.20260723T184607-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-24137 is a medium vulnerability (CVSS 5.8) in Sigstore, published January 22, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.39%, the 33rd percentile. Fixed in github.com/sigstore/sigstore 1.10.4.
References
github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf
github.com/sigstore/sigstore/commit/8ec410a2993ea78083aecf0e473a85453039496e
github.com/sigstore/sigstore/releases/tag/v1.10.4
nvd.nist.gov/vuln/detail/CVE-2026-24137
pkg.go.dev/vuln/GO-2026-4358
github.com/advisories/GHSA-fcv2-xgw5-pqxf
Show 194 moreShow less
github.com/CVEProject/cvelistV5/tree/main/cves/2026/24xxx/CVE-2026-24137.json
security-tracker.debian.org/tracker/CVE-2026-24137
github.com/sigstore/sigstore
suse.com/support/update/announcement/2026/suse-su-20260592-1
bugzilla.suse.com/1234486
bugzilla.suse.com/1237611
bugzilla.suse.com/1238683
bugzilla.suse.com/1239186
bugzilla.suse.com/1239323
bugzilla.suse.com/1240444
bugzilla.suse.com/1253802
bugzilla.suse.com/1256535
bugzilla.suse.com/1257138
suse.com/security/cve/CVE-2024-45337
suse.com/security/cve/CVE-2025-22868
suse.com/security/cve/CVE-2025-22869
suse.com/security/cve/CVE-2025-22870
suse.com/security/cve/CVE-2025-27144
suse.com/security/cve/CVE-2025-30204
suse.com/security/cve/CVE-2025-58181
suse.com/security/cve/CVE-2026-22772
suse.com/security/cve/CVE-2026-24137
suse.com/support/update/announcement/2026/suse-su-20260757-1
suse.com/security/cve/CVE-2017-18873
suse.com/security/cve/CVE-2017-18903
suse.com/security/cve/CVE-2017-18906
suse.com/security/cve/CVE-2017-18907
suse.com/security/cve/CVE-2017-18908
suse.com/security/cve/CVE-2017-18909
suse.com/security/cve/CVE-2017-18911
suse.com/security/cve/CVE-2017-18912
suse.com/security/cve/CVE-2017-18915
suse.com/security/cve/CVE-2017-18916
suse.com/security/cve/CVE-2017-18917
suse.com/security/cve/CVE-2017-18918
suse.com/security/cve/CVE-2023-43635
suse.com/security/cve/CVE-2023-43636
suse.com/security/cve/CVE-2023-43637
suse.com/security/cve/CVE-2025-13523
suse.com/security/cve/CVE-2025-13767
suse.com/security/cve/CVE-2025-13821
suse.com/security/cve/CVE-2025-14350
suse.com/security/cve/CVE-2025-14435
suse.com/security/cve/CVE-2025-14573
suse.com/security/cve/CVE-2025-14822
suse.com/security/cve/CVE-2025-50180
suse.com/security/cve/CVE-2025-64111
suse.com/security/cve/CVE-2025-64175
suse.com/security/cve/CVE-2025-64641
suse.com/security/cve/CVE-2025-65852
suse.com/security/cve/CVE-2025-66630
suse.com/security/cve/CVE-2025-67860
suse.com/security/cve/CVE-2025-70963
suse.com/security/cve/CVE-2026-0997
suse.com/security/cve/CVE-2026-0998
suse.com/security/cve/CVE-2026-0999
suse.com/security/cve/CVE-2026-20796
suse.com/security/cve/CVE-2026-21434
suse.com/security/cve/CVE-2026-21435
suse.com/security/cve/CVE-2026-21438
suse.com/security/cve/CVE-2026-22592
suse.com/security/cve/CVE-2026-22892
suse.com/security/cve/CVE-2026-23632
suse.com/security/cve/CVE-2026-23633
suse.com/security/cve/CVE-2026-23644
suse.com/security/cve/CVE-2026-23989
suse.com/security/cve/CVE-2026-23991
suse.com/security/cve/CVE-2026-23992
suse.com/security/cve/CVE-2026-24051
suse.com/security/cve/CVE-2026-24122
suse.com/security/cve/CVE-2026-24135
suse.com/security/cve/CVE-2026-24686
suse.com/security/cve/CVE-2026-24834
suse.com/security/cve/CVE-2026-24845
suse.com/security/cve/CVE-2026-24851
suse.com/security/cve/CVE-2026-24894
suse.com/security/cve/CVE-2026-24895
suse.com/security/cve/CVE-2026-25120
suse.com/security/cve/CVE-2026-25140
suse.com/security/cve/CVE-2026-25229
suse.com/security/cve/CVE-2026-25232
suse.com/security/cve/CVE-2026-25242
suse.com/security/cve/CVE-2026-25518
suse.com/security/cve/CVE-2026-25591
suse.com/security/cve/CVE-2026-25760
suse.com/security/cve/CVE-2026-25766
suse.com/security/cve/CVE-2026-25791
suse.com/security/cve/CVE-2026-25793
suse.com/security/cve/CVE-2026-25802
suse.com/security/cve/CVE-2026-25804
suse.com/security/cve/CVE-2026-25882
suse.com/security/cve/CVE-2026-25889
suse.com/security/cve/CVE-2026-25890
suse.com/security/cve/CVE-2026-25891
suse.com/security/cve/CVE-2026-25899
suse.com/security/cve/CVE-2026-25934
suse.com/security/cve/CVE-2026-25935
suse.com/security/cve/CVE-2026-25949
suse.com/security/cve/CVE-2026-26014
suse.com/security/cve/CVE-2026-26055
suse.com/security/cve/CVE-2026-26056
suse.com/security/cve/CVE-2026-26187
suse.com/security/cve/CVE-2026-26190
suse.com/security/cve/CVE-2026-26201
suse.com/security/cve/CVE-2026-26205
suse.com/security/cve/CVE-2026-26313
suse.com/security/cve/CVE-2026-26314
suse.com/security/cve/CVE-2026-26315
suse.com/security/cve/CVE-2026-26957
suse.com/security/cve/CVE-2026-26958
suse.com/security/cve/CVE-2026-26963
suse.com/security/cve/CVE-2026-26995
suse.com/security/cve/CVE-2026-27017
suse.com/security/cve/CVE-2026-27111
suse.com/security/cve/CVE-2026-27112
suse.com/security/cve/CVE-2026-27141
suse.com/security/cve/CVE-2026-27571
suse.com/security/cve/CVE-2026-27585
suse.com/security/cve/CVE-2026-27586
suse.com/security/cve/CVE-2026-27587
suse.com/security/cve/CVE-2026-27588
suse.com/security/cve/CVE-2026-27589
suse.com/security/cve/CVE-2026-27590
suse.com/security/cve/CVE-2026-27598
suse.com/security/cve/CVE-2026-27611
suse.com/security/cve/CVE-2026-27626
suse.com/support/update/announcement/2026/suse-su-20260777-1
bugzilla.suse.com/1250620
bugzilla.suse.com/1253913
bugzilla.suse.com/1256496
bugzilla.suse.com/1256562
bugzilla.suse.com/1257080
bugzilla.suse.com/1257085
bugzilla.suse.com/1257139
bugzilla.suse.com/1258542
bugzilla.suse.com/1258612
suse.com/security/cve/CVE-2025-11065
suse.com/security/cve/CVE-2026-22703
suse.com/support/update/announcement/2026/suse-su-202620904-1
suse.com/support/update/announcement/2026/suse-su-20262609-1
bugzilla.suse.com/1260311
bugzilla.suse.com/1262956
bugzilla.suse.com/1264177
bugzilla.suse.com/1265844
bugzilla.suse.com/1266202
bugzilla.suse.com/1266656
bugzilla.suse.com/1267982
suse.com/security/cve/CVE-2026-33186
suse.com/security/cve/CVE-2026-33814
suse.com/security/cve/CVE-2026-34986
suse.com/security/cve/CVE-2026-39821
suse.com/security/cve/CVE-2026-39827
suse.com/security/cve/CVE-2026-39828
suse.com/security/cve/CVE-2026-39829
suse.com/security/cve/CVE-2026-39830
suse.com/security/cve/CVE-2026-39831
suse.com/security/cve/CVE-2026-39832
suse.com/security/cve/CVE-2026-39833
suse.com/security/cve/CVE-2026-39834
suse.com/security/cve/CVE-2026-39835
suse.com/security/cve/CVE-2026-42508
suse.com/security/cve/CVE-2026-46595
suse.com/security/cve/CVE-2026-46597
suse.com/security/cve/CVE-2026-46598
suse.com/security/cve/CVE-2026-48785
ubuntu.com/security/CVE-2026-24137
cve.org/CVERecord?id=CVE-2026-24137
bugzilla.suse.com/1228324
bugzilla.suse.com/1234595
bugzilla.suse.com/1234794
bugzilla.suse.com/1235211
bugzilla.suse.com/1236528
bugzilla.suse.com/1237679
bugzilla.suse.com/1238611
bugzilla.suse.com/1239341
bugzilla.suse.com/1253924
bugzilla.suse.com/1255462
bugzilla.suse.com/1258047
bugzilla.suse.com/1258048
suse.com/security/cve/CVE-2023-45288
suse.com/security/cve/CVE-2024-28180
suse.com/security/cve/CVE-2024-3727
suse.com/security/cve/CVE-2024-41110
suse.com/security/cve/CVE-2024-45338
suse.com/security/cve/CVE-2025-22872
suse.com/security/cve/CVE-2025-47911
suse.com/security/cve/CVE-2025-47913
suse.com/security/cve/CVE-2025-47914
suse.com/security/cve/CVE-2025-58190
suse.com/security/cve/CVE-2025-65105
suse.com/security/cve/CVE-2025-8556
suse.com/security/cve/CVE-2016-11063
suse.com/security/cve/CVE-2016-11066
suse.com/security/cve/CVE-2016-11067
Left out here: 1,600 references and the rest of 5 source descriptions. The JSON record has them.