CVE-2026-118763

HIGHPre-NVD 7.47.4
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-10-30. A secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-113272 (ENISA EUVD) · GHSA-j63v-mwhm-56jx (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 0.7.2, packages/oci/src/registry.ts contains a RegistryClient.signIn() method that stores registry Authorization and Docker configuration headers as defaults on a shared HTTP client, while RegistryClient.uploadBlob() sends a fresh PUT to an absolute blob-upload Location supplied by the registry without checking that its origin or scheme matches the registry. A malicious or compromised registry can therefore direct a user pushing an artifact through attachArtifactToImage() to an attacker-controlled host and receive the registry bearer token, Basic credentials, or custom authentication headers. Redirect-time header stripping does not prevent the leak because the cross-host PUT is a new explicit request rather than a followed redirect. This is a residual of CVE-2026-59891, whose fix changed credential selection in credentials.ts but did not constrain where credentials are sent from registry.ts. Version 0.7.2 fixes the issue by separating registry credentials from client-wide defaults and sending them only to the registry origin.

CVSS v3
7.4
EG Score
7.4HIGHhigh confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-13). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 29, 2026

Last Modified

October 30, 2026

Advisory Details (4)

Auto-updated Oct 29, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github, github_commit.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

@sigstore/oci sends the registry Authorization header to a cross-host blob-upload Location · Advisory · sigstore/sigstore-js · GitHub

https://github.com/sigstore/sigstore-js/security/advisories/GHSA-j63v-mwhm-56jx
GitHub pull request

Harden OCI registry request handling

Fix merged in sigstore/sigstore-js PR #1762 on 2026-10-29 — awaiting tagged release

https://github.com/sigstore/sigstore-js/pull/1762
GitHub commit

commit e4ca65c3ab3c (sigstore/sigstore-js)

Fix landed in sigstore/sigstore-js commit e4ca65c3ab3c — awaiting tagged release

https://github.com/sigstore/sigstore-js/commit/e4ca65c3ab3c675456ab9b0bd04217ceccad3558
GitHub commit Patch Available

commit b855f46cfe81 (sigstore/sigstore-js)

Patch available: sigstore/sigstore-js @sigstore/[email protected] (contains commit b855f46cfe81)

https://github.com/sigstore/sigstore-js/commit/b855f46cfe81f26481c6d3f4b333dfd00f2fd1b1

Vendor Advisories for CVE-2026-118763(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@sigstore/oci @ 0.7.2 (fixes <= 0.7.1)—ghsa

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@sigstore/oci—
  • every version up to 0.7.2: fixed in 0.7.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 23:49 UTCEchelonGraph re-scored
  2. 2026-11-13 23:49 UTCGHSA enrichmentGHSA-j63v-mwhm-56jx · GitHub severity HIGH · GitHub CVSS 7.4
  3. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  5. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  6. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  7. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  8. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  9. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-11-06 18:32 UTCEchelonGraph re-scored
  11. 2026-11-06 18:32 UTCGHSA enrichmentGHSA-j63v-mwhm-56jx · GitHub severity HIGH · GitHub CVSS 7.4
  12. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  18. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-30 18:26 UTCEchelonGraph re-scored
  20. 2026-10-30 17:21 UTCEchelonGraph re-scored
  21. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-29 18:02 UTCENISA EUVD ID recordedEUVD-2026-113272 · Source: ENISA EUVD
  23. 2026-10-29 17:27 UTCEchelonGraph re-scored
  24. 2026-10-29 17:17 UTCEchelonGraph re-scoredFirst assessed: 7.4 HIGH
  25. 2026-10-29 17:16 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

1 shown

npm:@sigstore/oci

Frequently asked(5)

What is CVE-2026-118763?
CVE-2026-118763 is a high-severity vulnerability; its CVE record was published on October 29, 2026. sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 0.7.2, packages/oci/src/registry.ts contains a RegistryClient.signIn() method that stores registry Authorization and Docker configuration headers as defaults on a shared HTTP client, while…
When was the CVE record for CVE-2026-118763 published?
The CVE record for CVE-2026-118763 was published on October 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-118763 actively exploited?
CVE-2026-118763 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118763?
CVE-2026-118763 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-118763?
A fix for CVE-2026-118763 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-118763 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-118763

Explore →

Is Your Infrastructure Affected by CVE-2026-118763?

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

Book a Demo →Browse All CVEs