github.com/sigstore/fulcio
Affected
- introduced
0, fixed1.8.6(semver)
Fixed versions
1.8.6
Fix
- Fixed version
1.8.6go get github.com/sigstore/[email protected]
Advisory
Also known as: CVE-2026-49478, GO-2026-5853
Fulcio has OIDC Discovery Redirect Following Allows SSRF and JWKS Substitution for Meta-Issuer Paths, with Kubernetes Service-Account Token Leakage
Impact
Three security vulnerabilities were identified in the OIDC Discovery client:
/.well-known/openid-configuration). Prior to this fix, if a configured issuer returned an HTTP redirect to a different host, the client followed it by default. This allowed a compromised or malicious issuer to redirect Fulcio's discovery requests to internal-only systems, resulting in blind SSRF.jwks_uri pointing to an attacker-controlled host. When Fulcio successfully initialized the provider and cached the resulting verifier in the verifier cache, it poisoned the cache with the attacker's verification keys. The attacker could then present signatures validated against the poisoned keys.https://kubernetes.default.svc).jwks_uri pointed to a different domain.MetaIssuer of type kubernetes (e.g., matching external EKS/GKE endpoints) was matched, and a local Kubernetes issuer was present in the config, the transport loaded and attached the local in-cluster ServiceAccount token to outbound requests sent to the external host.Patches
The following mitigations have been applied:
https://kubernetes.default.svc).Workarounds
None, upgrade to v1.8.6
High Basis: The source's own band: HIGH
0, fixed 1.8.6 (semver)1.8.6
1.8.6go get github.com/sigstore/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0