CVE-2026-49478

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

A fix is available — apply it.

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.

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 computed
Severity87% × 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, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v1.8.6

Patch available: sigstore/fulcio v1.8.6

https://github.com/sigstore/fulcio/releases/tag/v1.8.6
github_commit

commit 378c654f48c3 (sigstore/fulcio)

Fix landed in sigstore/fulcio commit 378c654f48c3 — awaiting tagged release

https://github.com/sigstore/fulcio/commit/378c654f48c3bafdced04ead7010aab2cb4c6ca1
github_pr

Block 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/2354
github Patch Available

OIDC 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-6hh6

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatadvanced-cluster-security/rhacs-main-rhel8:17854209592026-07-30redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17854132102026-07-30redhat

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)
PackageVulnerable rangeFixed inDependents
golang-github-sigstore-fulcio1.6.5-1, 1.7.1-1, 1.8.5-1, 1.8.7-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-github-sigstore-fulcio1.6.5-1, 1.7.1-1, 1.8.5-11.8.7-1
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/sigstore/fulcio1.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.

  1. 2026-08-21 07:11 UTCEG score recompute
  2. 2026-08-21 07:11 UTCVendor advisory
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 18:12 UTCVendor advisory
  5. 2026-08-20 05:30 UTCEG score recompute
  6. 2026-08-20 05:30 UTCVendor advisory
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 12:34 UTCVendor advisory
  9. 2026-08-18 23:00 UTCEG score recompute
  10. 2026-08-18 23:00 UTCVendor advisory
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 00:01 UTCEG score recompute
  13. 2026-08-18 00:01 UTCVendor advisory
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 07:08 UTCVendor advisory
  16. 2026-08-16 18:26 UTCEG score recompute
  17. 2026-08-16 18:26 UTCVendor advisory
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 05:43 UTCEG score recompute
  20. 2026-08-16 05:43 UTCVendor advisory
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 17:02 UTCVendor advisory
  23. 2026-08-15 04:20 UTCEG score recompute
  24. 2026-08-15 04:20 UTCVendor advisory
  25. 2026-08-15 03:23 UTCEG score recompute
Show 35 more
  1. 2026-08-15 03:23 UTCVendor advisory
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 15:00 UTCVendor advisory
  4. 2026-08-14 02:18 UTCVendor advisory
  5. 2026-08-13 13:36 UTCEG score recompute
  6. 2026-08-13 13:36 UTCVendor advisory
  7. 2026-08-13 13:18 UTCVendor advisory
  8. 2026-08-13 02:35 UTCVendor advisory
  9. 2026-08-12 13:53 UTCVendor advisory
  10. 2026-08-12 01:11 UTCVendor advisory
  11. 2026-08-11 12:29 UTCVendor advisory
  12. 2026-08-10 23:41 UTCVendor advisory
  13. 2026-08-10 10:59 UTCVendor advisory
  14. 2026-08-09 22:14 UTCVendor advisory
  15. 2026-08-09 09:32 UTCVendor advisory
  16. 2026-08-08 20:50 UTCVendor advisory
  17. 2026-08-08 08:08 UTCVendor advisory
  18. 2026-08-07 19:26 UTCVendor advisory
  19. 2026-08-07 06:44 UTCVendor advisory
  20. 2026-08-06 18:02 UTCVendor advisory
  21. 2026-08-06 05:20 UTCVendor advisory
  22. 2026-08-05 16:38 UTCVendor advisory
  23. 2026-08-04 22:07 UTCVendor advisory
  24. 2026-08-04 08:44 UTCVendor advisory
  25. 2026-08-03 18:25 UTCVendor advisory
  26. 2026-08-03 04:55 UTCVendor advisory
  27. 2026-08-02 16:13 UTCVendor advisory
  28. 2026-08-02 03:31 UTCVendor advisory
  29. 2026-08-01 14:48 UTCVendor advisory
  30. 2026-08-01 02:06 UTCVendor advisory
  31. 2026-07-31 12:43 UTCVendor advisory
  32. 2026-07-30 11:07 UTCEG score recompute
  33. 2026-07-26 13:51 UTCEG score recompute
  34. 2026-07-23 03:18 UTCEG score recompute
  35. 2026-06-30 19:31 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49478?
CVE-2026-49478 is a high vulnerability published on June 30, 2026. 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…
When was CVE-2026-49478 disclosed?
CVE-2026-49478 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on August 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49478 actively exploited?
CVE-2026-49478 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.2% of all scored CVEs.
What is the CVSS score of CVE-2026-49478?
CVE-2026-49478 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-49478?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49478, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49478

Explore →

Is Your Infrastructure Affected by CVE-2026-49478?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.