CVE-2026-22772: Fulcio vulnerable to Server-Side Request Forgery (SSRF) via MetaIssuer Regex Bypass

Published Jan 12, 2026
·
Updated

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)

go 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 jwksuri pointing to internal service 7. Fulcio fetches from internal service → SSRF

Other sources

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.

MITRE

Affected Software

3 affected componentsFixes available
Fulcio Fulcio<1.8.5
go/github.com/sigstore/fulcio<=1.8.4
1.8.5
linuxfoundation Fulcio<1.8.5

Event History

Jan 12, 2026
CVE Published
via MITRE·08:58 PM
Data Sourced
via MITRE·08:58 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
RemedyAffected Software
Jan 13, 2026
Advisory Published
via GitHub·06:47 PM
Data Sourced
via GitHub·06:47 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-22772?

CVE-2026-22772 is rated as a medium severity vulnerability due to its potential for exploitation through server-side request forgery.

2

How do I fix CVE-2026-22772?

To fix CVE-2026-22772, upgrade Fulcio to version 1.8.5 or later, where the vulnerability has been addressed.

3

What impact does CVE-2026-22772 have on Fulcio?

CVE-2026-22772 allows attackers to bypass the MetaIssuer checks through server-side request forgery, potentially compromising certificate issuance.

4

Which versions of Fulcio are affected by CVE-2026-22772?

Fulcio versions prior to 1.8.5 are affected by CVE-2026-22772 and are vulnerable to the exploit.

5

Is CVE-2026-22772 an exploit that can be easily executed?

While CVE-2026-22772 requires specific conditions to execute, its presence can pose significant security risks if left unpatched.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203