Every CVE Search/ Get API key

CVE-2026-22772

Fulcio vulnerable to Server-Side Request Forgery (SSRF) via MetaIssuer Regex Bypass

5.8 MediumFix available

Fulcio is a certificate authority for issuing code signing certificates for an OpenID Connect (OIDC) identity. Prior to 1.8.5, Fulcio's metaRegex() function uses unanchored regex, allowing attackers to bypass MetaIssuer URL validation and trigger SSRF to arbitrary internal services. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. This vulnerability is fixed in 1.8.5.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
Low
Privileges needed
None
User interaction
None

What an attacker can affect

Confidentiality
Low
Integrity
None
Availability
None

Exploit likelihood

0.23%Up 0.2 points since Jan 13, 2026
90%50%10%1%

What each source reports

CVE List Score used 5.8

Fulcio vulnerable to Server-Side Request Forgery (SSRF) via MetaIssuer Regex Bypass

Fulcio is a certificate authority for issuing code signing certificates for an OpenID Connect (OIDC) identity. Prior to 1.8.5, Fulcio's metaRegex() function uses unanchored regex, allowing attackers to bypass MetaIssuer URL validation and trigger SSRF to arbitrary internal services. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. This vulnerability is fixed in 1.8.5.

Record
CVE-2026-22772
CVSS 3.1
5.8 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Weakness
CWE-918
Updated
2026-11-02
EUVDEUVD-2026-2001 5.8

Fulcio is a certificate authority for issuing code signing certificates for an OpenID Connect (OIDC) identity. Prior to 1.8.5, Fulcio's metaRegex() function uses unanchored regex, allowing attackers to bypass MetaIssuer URL validation and trigger SSRF to arbitrary internal services. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. This vulnerability is fixed in 1.8.5.

Record
EUVD-2026-2001
CVSS 3.1
5.8 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Updated
2026-11-02
GitHub AdvisoriesGHSA-59jp-pj84-45mr 5.8

Fulcio is vulnerable to Server-Side Request Forgery (SSRF) via MetaIssuer Regex Bypass

Security Disclosure: SSRF via MetaIssuer Regex Bypass

Summary

Fulcio's metaRegex() function uses unanchored regex, allowing attackers to bypass MetaIssuer URL validation and trigger SSRF to arbitrary internal services.

Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF.

Impact

  • SSRF to cloud metadata (169.254.169.254)
  • SSRF to internal Kubernetes APIs
  • SSRF to any service accessible from Fulcio's network
  • Affects ALL deployments using MetaIssuers

Patches

Upgrade to v1.8.5.

Workarounds

None. If anchors are included in the meta issuer configuration URL, they will be escaped before the regular expression is compiled, not making this a sufficient mitigation. Deployments must upgrade to the latest Fulcio release v1.8.5.

Affected Code

File: pkg/config/config.go
Function: metaRegex() (lines 143-156)

func metaRegex(issuer string) (*regexp.Regexp, error) {
    quoted := regexp.QuoteMeta(issuer)
    replaced := strings.ReplaceAll(quoted, regexp.QuoteMeta("*"), "[-_a-zA-Z0-9]+")
    return regexp.Compile(replaced)  // Missing ^ and $ anchors
}

The Bug

The regex has no ^ (start) or $ (end) anchors. Go's regexp.MatchString() does substring matching, so:

Pattern:  https://oidc.eks.*.amazonaws.com/id/*
Regex:    https://oidc\.eks\.[-_a-zA-Z0-9]+\.amazonaws\.com/id/[-_a-zA-Z0-9]+

Input:    https://attacker.com/x/https://oidc.eks.foo.amazonaws.com/id/bar
Result:   MATCHES (substring found)

Exploit

  1. Attacker sends JWT with iss claim: https://attacker.com/path/https://oidc.eks.x.amazonaws.com/id/y
  2. Fulcio's GetIssuer() matches this against MetaIssuer patterns
  3. Unanchored regex matches the embedded pattern as substring
  4. Fulcio calls oidc.NewProvider() with attacker's URL
  5. HTTP request goes to attacker.com, not amazonaws.com
  6. Attacker returns OIDC discovery with jwks_uri pointing to internal service
  7. Fulcio fetches from internal service → SSRF
Record
GHSA-59jp-pj84-45mr
CVSS 3.1
5.8 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Weakness
CWE-918
Updated
2026-11-02
NVD 5.8

Fulcio is a certificate authority for issuing code signing certificates for an OpenID Connect (OIDC) identity. Prior to 1.8.5, Fulcio's metaRegex() function uses unanchored regex, allowing attackers to bypass MetaIssuer URL validation and trigger SSRF to arbitrary internal services. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. This vulnerability is fixed in 1.8.5.

Record
CVE-2026-22772
CVSS 3.1
5.8 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
CVSS 3.1
5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness
CWE-918
Updated
2026-11-02
OSV 5.8

Fulcio vulnerable to Server-Side Request Forgery (SSRF) via MetaIssuer Regex Bypass

Fulcio is a certificate authority for issuing code signing certificates for an OpenID Connect (OIDC) identity. Prior to 1.8.5, Fulcio's metaRegex() function uses unanchored regex, allowing attackers to bypass MetaIssuer URL validation and trigger SSRF to arbitrary internal services. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. This vulnerability is fixed in 1.8.5.

Record
CVE-2026-22772
CVSS 3.1
5.8 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Weakness
CWE-918
Updated
2026-11-02
OSVDEBIAN-CVE-2026-22772 5.3

Fulcio is a certificate authority for issuing code signing certificates for an OpenID Connect (OIDC) identity. Prior to 1.8.5, Fulcio's metaRegex() function uses unanchored regex, allowing attackers to bypass MetaIssuer URL validation and trigger SSRF to arbitrary internal services. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. This vulnerability is fixed in 1.8.5.

Record
DEBIAN-CVE-2026-22772
CVSS 3.1
5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Updated
2026-11-02
Show 14 moreShow less
OSVGHSA-59jp-pj84-45mr 5.8

Fulcio is vulnerable to Server-Side Request Forgery (SSRF) via MetaIssuer Regex Bypass

Security Disclosure: SSRF via MetaIssuer Regex Bypass

Summary

Fulcio's metaRegex() function uses unanchored regex, allowing attackers to bypass MetaIssuer URL validation and trigger SSRF to arbitrary internal services.

Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF.

Impact

  • SSRF to cloud metadata (169.254.169.254)
  • SSRF to internal Kubernetes APIs
  • SSRF to any service accessible from Fulcio's network
  • Affects ALL deployments using MetaIssuers

Patches

Upgrade to v1.8.5.

Workarounds

None. If anchors are included in the meta issuer configuration URL, they will be escaped before the regular expression is compiled, not making this a sufficient mitigation. Deployments must upgrade to the latest Fulcio release v1.8.5.

Affected Code

File: pkg/config/config.go
Function: metaRegex() (lines 143-156)

func metaRegex(issuer string) (*regexp.Regexp, error) {
    quoted := regexp.QuoteMeta(issuer)
    replaced := strings.ReplaceAll(quoted, regexp.QuoteMeta("*"), "[-_a-zA-Z0-9]+")
    return regexp.Compile(replaced)  // Missing ^ and $ anchors
}

The Bug

The regex has no ^ (start) or $ (end) anchors. Go's regexp.MatchString() does substring matching, so:

Pattern:  https://oidc.eks.*.amazonaws.com/id/*
Regex:    https://oidc\.eks\.[-_a-zA-Z0-9]+\.amazonaws\.com/id/[-_a-zA-Z0-9]+

Input:    https://attacker.com/x/https://oidc.eks.foo.amazonaws.com/id/bar
Result:   MATCHES (substring found)

Exploit

  1. Attacker sends JWT with iss claim: https://attacker.com/path/https://oidc.eks.x.amazonaws.com/id/y
  2. Fulcio's GetIssuer() matches this against MetaIssuer patterns
  3. Unanchored regex matches the embedded pattern as substring
  4. Fulcio calls oidc.NewProvider() with attacker's URL
  5. HTTP request goes to attacker.com, not amazonaws.com
  6. Attacker returns OIDC discovery with jwks_uri pointing to internal service
  7. Fulcio fetches from internal service → SSRF
Record
GHSA-59jp-pj84-45mr
CVSS 3.1
5.8 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Weakness
CWE-918
Updated
2026-11-02
OSVUBUNTU-CVE-2026-22772 5.8

Fulcio is a certificate authority for issuing code signing certificates for an OpenID Connect (OIDC) identity. Prior to 1.8.5, Fulcio's metaRegex() function uses unanchored regex, allowing attackers to bypass MetaIssuer URL validation and trigger SSRF to arbitrary internal services. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. This vulnerability is fixed in 1.8.5.

Record
UBUNTU-CVE-2026-22772
CVSS 3.1
5.8 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
CVSS 3.1
5.3 MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Updated
2026-11-02
OSVGO-2026-4311 No score

Fulcio is vulnerable to Server-Side Request Forgery (SSRF) via MetaIssuer Regex Bypass in github.com/sigstore/fulcio

Fulcio is vulnerable to Server-Side Request Forgery (SSRF) via MetaIssuer Regex Bypass in github.com/sigstore/fulcio

Record
GO-2026-4311
Updated
2026-11-02
OSVopenSUSE-RU-2026:20161-1 No score

Recommended update for hauler

This update for hauler fixes the following issues:

Changes in hauler:

  • Update to version 1.4.1 (bsc#1256546, CVE-2026-22772):

    • fixed typos for containerd imports (#493)
    • fix and support containerd imports of hauls (#492)
    • bump github.com/sigstore/fulcio (#489)

  • Update to version 1.4.0:

    • added/updated logging for serve and remove (#487)
    • added/fixed helm chart images/dependencies features (#485)
    • more experimental feature updates (#486)
    • add experimental notes (#483)
    • updated tempdir flag to store persistent flags (#484)
    • delete artifacts from store (#473)
    • path rewrites (#475)
    • updated/fixed workflow dependency versions (#478)

  • Update to version 1.3.2:

    • bump to latest cosign fork release (#481)
    • Bump golang.org/x/crypto in the go_modules group across 1 directory (#476)
Record
openSUSE-RU-2026:20161-1
Updated
2026-11-02
OSVopenSUSE-SU-2026:10068-1 No score

hauler-1.4.1-1.1 on GA media

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

Record
openSUSE-SU-2026:10068-1
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: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: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:0292-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

Update to version 0.0.20260123T022811 2026-01-23T02:28:11Z (jsc#PED-11136). Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2025-3764 CVE-2024-44905 GHSA-6xp3-p59p-q4fj
  • GO-2025-4188 CVE-2025-65637 GHSA-4f99-4q7p-p3gh
  • GO-2025-4252 CVE-2025-68383 GHSA-2mj3-6grc-px38
  • GO-2025-4253 CVE-2025-68388 GHSA-fj69-23m4-ccvv
  • GO-2026-4310 CVE-2026-22689 GHSA-524m-q5m7-79mm
  • GO-2026-4311 CVE-2026-22772 GHSA-59jp-pj84-45mr
  • GO-2026-4312 CVE-2026-22771 GHSA-xrwg-mqj6-6m22
  • GO-2026-4313 CVE-2026-22786 GHSA-3558-j79f-vvm6
  • GO-2026-4314 CVE-2026-22868 GHSA-mq3p-rrmp-79jg
  • GO-2026-4315 CVE-2026-22862 GHSA-mr7q-c9w9-wh4h
  • GO-2026-4316 GHSA-mqqf-5wvp-8fh8
  • GO-2026-4317 CVE-2017-18892 GHSA-wj5w-qghh-gvqp
  • GO-2026-4318 CVE-2025-66292 GHSA-vh2x-fw87-4fxq
  • GO-2026-4319 CVE-2026-23511 GHSA-pvm5-9frx-264r
  • GO-2026-4320 CVE-2026-23520 GHSA-gjqq-6r35-w3r8
  • GO-2026-4321 CVE-2025-68671 GHSA-f2ph-gc9m-q55f
  • GO-2026-4322 CVE-2026-22045 GHSA-cwjm-3f7h-9hwq
Record
SUSE-SU-2026:0292-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: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

Affected products

Affected packages

Affected packages
PackageAffectedFixed
github.com/sigstore/fulcio
Go
 through 1.8.4
1.8.5
golang-github-sigstore-fulcio
Debian:13
 All versions, plus listed versions
1.6.5-11.7.1-11.8.5-11.8.7-11.8.8-1
 None known
golang-github-sigstore-fulcio
Debian:14
 before 1.8.5-1, plus listed versions
1.6.5-11.7.1-1
1.8.5-1
github.com/sigstore/fulcio
Go
 before 1.8.5
1.8.5
govulncheck-vulndb
openSUSE:Leap 15.6
From an advisory covering 16 CVEs
 before 0.0.20260123T022811-150000.1.140.1
0.0.20260123T022811-150000.1.140.1
vexctl
openSUSE: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
cosign
SUSE: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
cosign
openSUSE:Leap 15.6
From an advisory covering 9 CVEs
 before 3.0.5-150400.3.35.1
3.0.5-150400.3.35.1
cosign
SUSE:Linux Enterprise Server 16.0
From an advisory covering 9 CVEs
 before 3.0.5-160000.1.1
3.0.5-160000.1.1
cosign
SUSE: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 10 moreShow less
Affected packages
PackageAffectedFixed
golang-github-sigstore-fulcio
Ubuntu:25.10
 All versions, plus listed versions
1.6.5-1
 None known
golang-github-sigstore-fulcio
Ubuntu:26.10
 All versions, plus listed versions
1.7.1-11.8.7-11.8.8-1
 None known
golang-github-sigstore-fulcio
Ubuntu:26.04:LTS
 All versions, plus listed versions
1.6.5-11.7.1-1
 None known
hauler
openSUSE:Leap 16.0
 before 1.4.1-bp160.1.1
1.4.1-bp160.1.1
hauler
openSUSE:Tumbleweed
 before 1.4.1-1.1
1.4.1-1.1
vexctl
openSUSE:Tumbleweed
From an advisory covering 9 CVEs
 before 0.4.1+git78.f951e3a-1.1
0.4.1+git78.f951e3a-1.1
cosign
openSUSE:Tumbleweed
From an advisory covering 6 CVEs
 before 3.0.5-1.1
3.0.5-1.1
cosign
openSUSE:Leap 16.0
From an advisory covering 9 CVEs
 before 3.0.5-160000.1.1
3.0.5-160000.1.1
vexctl
openSUSE: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-vulndb
openSUSE:Leap 16.0
From an advisory covering 1734 CVEs
 before 0.0.20260723T184607-160000.1.1
0.0.20260723T184607-160000.1.1

History

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

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

In short

CVE-2026-22772 is a medium vulnerability (CVSS 5.8) in Linuxfoundation Fulcio, published January 12, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.23%, the 14th percentile. Fixed in github.com/sigstore/fulcio 1.8.5.

References

Show 194 moreShow less
This page doesn't list everything

Left out here: 1,572 references and the rest of 3 source descriptions. The JSON record has them.

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