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.2%, top 93% 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
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.3%CVSS: 8.7Exploit: None knownExposed services: Not assessed

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.7HIGHmedium confidence
EG Risk
39
EG Risk 39/100

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%
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

Published

June 30, 2026

Last Modified

September 9, 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

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
golang-github-sigstore-fulcio1.6.5-1, 1.7.1-1, 1.8.5-1, 1.8.7-1, 1.8.8-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-sigstore-fulcio1.6.5-1, 1.7.1-1, 1.8.5-1
  • every version up to 1.8.7-1: fixed in 1.8.7-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/sigstore/fulcio—
  • every version up to 1.8.6: fixed in 1.8.6
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 32× 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.

Showing the most recent 100 of 117 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-01 19:50 UTCEPSS rescore
  4. 2026-09-30 15:03 UTCEPSS rescore
  5. 2026-09-28 13:51 UTCEPSS rescore
  6. 2026-09-27 13:48 UTCEPSS rescore
  7. 2026-09-26 15:59 UTCEPSS rescore
  8. 2026-09-26 00:27 UTCEPSS rescore
  9. 2026-09-23 17:53 UTCEPSS rescore
  10. 2026-09-23 07:19 UTCEG score recompute
  11. 2026-09-23 07:19 UTCVendor advisory
  12. 2026-09-20 20:16 UTCEPSS rescore
  13. 2026-09-18 19:28 UTCEPSS rescore
  14. 2026-09-18 06:48 UTCEG score recompute
  15. 2026-09-18 06:48 UTCVendor advisory
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-14 00:47 UTCEG score recompute
  19. 2026-09-14 00:47 UTCVendor advisory
  20. 2026-09-13 16:47 UTCEPSS rescore
  21. 2026-09-13 09:16 UTCVendor advisory
  22. 2026-09-12 15:09 UTCEG score recompute
  23. 2026-09-12 15:09 UTCVendor advisory
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-10 09:35 UTCEPSS rescore
Show 75 more
  1. 2026-09-09 22:59 UTCEG score recompute
  2. 2026-09-09 22:59 UTCVendor advisory
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 14:35 UTCEG score recompute
  6. 2026-09-06 14:35 UTCVendor advisory
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-01 13:54 UTCEPSS rescore
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 18:01 UTCEG score recompute
  12. 2026-08-30 18:01 UTCVendor advisory
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 22:41 UTCEG score recompute
  16. 2026-08-27 22:41 UTCVendor advisory
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 01:20 UTCEG score recompute
  21. 2026-08-25 01:20 UTCVendor advisory
  22. 2026-08-24 12:38 UTCEG score recompute
  23. 2026-08-24 12:38 UTCVendor advisory
  24. 2026-08-23 23:10 UTCVendor advisory
  25. 2026-08-23 10:28 UTCEG score recompute
  26. 2026-08-23 10:28 UTCVendor advisory
  27. 2026-08-23 00:19 UTCEPSS rescore
  28. 2026-08-22 21:46 UTCVendor advisory
  29. 2026-08-22 08:36 UTCEG score recompute
  30. 2026-08-22 08:36 UTCVendor advisory
  31. 2026-08-21 23:49 UTCEPSS rescore
  32. 2026-08-21 19:54 UTCVendor advisory
  33. 2026-08-21 07:11 UTCEG score recompute
  34. 2026-08-21 07:11 UTCVendor advisory
  35. 2026-08-20 22:55 UTCEPSS rescore
  36. 2026-08-20 18:12 UTCVendor advisory
  37. 2026-08-20 05:30 UTCEG score recompute
  38. 2026-08-20 05:30 UTCVendor advisory
  39. 2026-08-19 17:04 UTCEPSS rescore
  40. 2026-08-19 12:34 UTCVendor advisory
  41. 2026-08-18 23:00 UTCEG score recompute
  42. 2026-08-18 23:00 UTCVendor advisory
  43. 2026-08-18 13:48 UTCEPSS rescore
  44. 2026-08-18 00:01 UTCEG score recompute
  45. 2026-08-18 00:01 UTCVendor advisory
  46. 2026-08-17 13:47 UTCEPSS rescore
  47. 2026-08-17 07:08 UTCVendor advisory
  48. 2026-08-16 18:26 UTCEG score recompute
  49. 2026-08-16 18:26 UTCVendor advisory
  50. 2026-08-16 14:56 UTCEPSS rescore
  51. 2026-08-16 05:43 UTCEG score recompute
  52. 2026-08-16 05:43 UTCVendor advisory
  53. 2026-08-16 02:14 UTCEPSS rescore
  54. 2026-08-15 17:02 UTCVendor advisory
  55. 2026-08-15 04:20 UTCEG score recompute
  56. 2026-08-15 04:20 UTCVendor advisory
  57. 2026-08-15 03:23 UTCEG score recompute
  58. 2026-08-15 03:23 UTCVendor advisory
  59. 2026-08-15 01:30 UTCEPSS rescore
  60. 2026-08-14 15:00 UTCVendor advisory
  61. 2026-08-14 02:18 UTCVendor advisory
  62. 2026-08-13 13:36 UTCEG score recompute
  63. 2026-08-13 13:36 UTCVendor advisory
  64. 2026-08-13 13:18 UTCVendor advisory
  65. 2026-08-13 02:35 UTCVendor advisory
  66. 2026-08-12 13:53 UTCVendor advisory
  67. 2026-08-12 01:11 UTCVendor advisory
  68. 2026-08-11 12:29 UTCVendor advisory
  69. 2026-08-10 23:41 UTCVendor advisory
  70. 2026-08-10 10:59 UTCVendor advisory
  71. 2026-08-09 22:14 UTCVendor advisory
  72. 2026-08-09 09:32 UTCVendor advisory
  73. 2026-08-08 20:50 UTCVendor advisory
  74. 2026-08-08 08:08 UTCVendor advisory
  75. 2026-08-07 19:26 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Same product

2 shown

Debian:13:golang-github-sigstore-fulcio

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 on June 30, 2026, with the most recent update on September 9, 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.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49478?
CVE-2026-49478 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-49478?
A fix for CVE-2026-49478 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-49478 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs