Fulcio is a certificate authority for issuing code signing certificates for an OpenID Connect (OIDC) identity. Versions through 1.8.5 improperly follow cross-host redirects and attach Kubernetes ServiceAccount tokens during OIDC discovery, allowing a malicious or compromised issuer to perform blind SSRF, substitute and cache malicious JWKS keys, or disclose ServiceAccount tokens to external hosts. Version 1.8.6 blocks cross-host redirects, restricts token injection, and restricts local token loading. No known workarounds are available.
CVE-2026-49478
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
June 30, 2026
Last Modified
August 15, 2026
Advisory Details (4)
Auto-updated Aug 13, 2026v1.8.6
Patch available: sigstore/fulcio v1.8.6
https://github.com/sigstore/fulcio/releases/tag/v1.8.6commit 378c654f48c3 (sigstore/fulcio)
Fix landed in sigstore/fulcio commit 378c654f48c3 — awaiting tagged release
https://github.com/sigstore/fulcio/commit/378c654f48c3bafdced04ead7010aab2cb4c6ca1Block cross-host redirects and restrict bearer token to expected host
Fix merged in sigstore/fulcio PR #2354 on 2026-05-26 — awaiting tagged release
https://github.com/sigstore/fulcio/pull/2354OIDC Discovery Redirect Following Allows SSRF and JWKS Substitution for Meta-Issuer Paths, with Kubernetes Service-Account Token Leakage · Advisory · sigstore/fulcio · GitHub
https://github.com/sigstore/fulcio/security/advisories/GHSA-f5mr-q85p-6hh6Vendor Advisories for CVE-2026-49478(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:48913Red Hat Product SecurityHigh
Red Hat Security Advisory: RHACS 4.10.6 security and bug fix update
- RHSA-2026:48872Red Hat Product SecurityHigh
Red Hat Security Advisory: RHACS 4.9.10 security and bug fix update
- GHSA-f5mr-q85p-6hh6GitHub Security AdvisoriesHigh
Fulcio has OIDC Discovery Redirect Following Allows SSRF and JWKS Substitution for Meta-Issuer Paths, with Kubernetes Service-Account Token Leakage
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | advanced-cluster-security/rhacs-main-rhel8:1785420959 | 2026-07-30 | redhat |
| redhat | advanced-cluster-security/rhacs-main-rhel8:1785413210 | 2026-07-30 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(3 across 3 ecosystems)
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-github-sigstore-fulcio | 1.6.5-1, 1.7.1-1, 1.8.5-1, 1.8.7-1 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| golang-github-sigstore-fulcio | 1.6.5-1, 1.7.1-1, 1.8.5-1 | 1.8.7-1 | — |
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/sigstore/fulcio | — | 1.8.6 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 28× in last 7d / 59× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 07:11 UTCEG score recompute
- 2026-08-21 07:11 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 18:12 UTCVendor advisory
- 2026-08-20 05:30 UTCEG score recompute
- 2026-08-20 05:30 UTCVendor advisory
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 12:34 UTCVendor advisory
- 2026-08-18 23:00 UTCEG score recompute
- 2026-08-18 23:00 UTCVendor advisory
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 00:01 UTCEG score recompute
- 2026-08-18 00:01 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 07:08 UTCVendor advisory
- 2026-08-16 18:26 UTCEG score recompute
- 2026-08-16 18:26 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 05:43 UTCEG score recompute
- 2026-08-16 05:43 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 17:02 UTCVendor advisory
- 2026-08-15 04:20 UTCEG score recompute
- 2026-08-15 04:20 UTCVendor advisory
- 2026-08-15 03:23 UTCEG score recompute
Show 35 moreShow fewer
- 2026-08-15 03:23 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 15:00 UTCVendor advisory
- 2026-08-14 02:18 UTCVendor advisory
- 2026-08-13 13:36 UTCEG score recompute
- 2026-08-13 13:36 UTCVendor advisory
- 2026-08-13 13:18 UTCVendor advisory
- 2026-08-13 02:35 UTCVendor advisory
- 2026-08-12 13:53 UTCVendor advisory
- 2026-08-12 01:11 UTCVendor advisory
- 2026-08-11 12:29 UTCVendor advisory
- 2026-08-10 23:41 UTCVendor advisory
- 2026-08-10 10:59 UTCVendor advisory
- 2026-08-09 22:14 UTCVendor advisory
- 2026-08-09 09:32 UTCVendor advisory
- 2026-08-08 20:50 UTCVendor advisory
- 2026-08-08 08:08 UTCVendor advisory
- 2026-08-07 19:26 UTCVendor advisory
- 2026-08-07 06:44 UTCVendor advisory
- 2026-08-06 18:02 UTCVendor advisory
- 2026-08-06 05:20 UTCVendor advisory
- 2026-08-05 16:38 UTCVendor advisory
- 2026-08-04 22:07 UTCVendor advisory
- 2026-08-04 08:44 UTCVendor advisory
- 2026-08-03 18:25 UTCVendor advisory
- 2026-08-03 04:55 UTCVendor advisory
- 2026-08-02 16:13 UTCVendor advisory
- 2026-08-02 03:31 UTCVendor advisory
- 2026-08-01 14:48 UTCVendor advisory
- 2026-08-01 02:06 UTCVendor advisory
- 2026-07-31 12:43 UTCVendor advisory
- 2026-07-30 11:07 UTCEG score recompute
- 2026-07-26 13:51 UTCEG score recompute
- 2026-07-23 03:18 UTCEG score recompute
- 2026-06-30 19:31 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-49478?
When was CVE-2026-49478 disclosed?
Is CVE-2026-49478 actively exploited?
What is the CVSS score of CVE-2026-49478?
How do I remediate CVE-2026-49478?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49478
Is Your Infrastructure Affected by CVE-2026-49478?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.