CVE-2026-119290

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-114136 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Zuke is a code-first, strongly typed build automation system for Deno. Prior to 1.51.0, @zuke/core writes rendered reportSummary(...) notes to GITHUB_STEP_SUMMARY through writeJobSummary without applying the redactor that protects resolved secret() values in console and persisted run output. A GitHub Actions build that places secret-derived text in a summary note can publish credentials in cleartext to everyone able to view the workflow run, including unauthenticated viewers of a public repository, and the durable summary remains exposed until the run is deleted. GitHub Actions masking directives do not protect the summary file, while runs outside GitHub Actions and builds that do not summarize secret-derived text are not affected. This issue is fixed in version 1.51.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
39th
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.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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 low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 30, 2026

Last Modified

October 30, 2026

Advisory Details (4)

Auto-updated Oct 30, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

core: v1.51.0

Patch available: zuke-build/zuke core-v1.51.0

https://github.com/zuke-build/zuke/releases/tag/core-v1.51.0
GitHub commit Patch Available

commit a46fd7287c91 (zuke-build/zuke)

Patch available: zuke-build/zuke prometheus-v1.1.1 (contains commit a46fd7287c91)

https://github.com/zuke-build/zuke/commit/a46fd7287c913d937b4d0bb46d0c22b87ddd8ba7
GitHub pull request Patch Available

feat(core): neutralise workflow-command sequences in GitHub-mode output and redact the job summary

Patch available: zuke-build/zuke prometheus-v1.1.1 (PR #547 merged 2026-09-10)

https://github.com/zuke-build/zuke/pull/547
GitHub advisoryMentions a patch (unverified)

Resolved secret() values are written to GITHUB_STEP_SUMMARY in the clear, disclosing them to anyone who can view the workflow run · Advisory · zuke-build/zuke · GitHub

https://github.com/zuke-build/zuke/security/advisories/GHSA-42wp-rrh6-vc23

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 15× 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-12 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-11-10 10:05 UTCEchelonGraph re-scored
  5. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-11-03 20:14 UTCEchelonGraph re-scored
  12. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-10-30 17:02 UTCENISA EUVD ID recordedEUVD-2026-114136 · Source: ENISA EUVD
  17. 2026-10-30 16:27 UTCEchelonGraph re-scored
  18. 2026-10-30 16:00 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  19. 2026-10-30 16:00 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-119290?
CVE-2026-119290 is a high-severity vulnerability; its CVE record was published on October 30, 2026. Zuke is a code-first, strongly typed build automation system for Deno. Prior to 1.51.0, @zuke/core writes rendered reportSummary(...) notes to GITHUB_STEP_SUMMARY through writeJobSummary without applying the redactor that protects resolved secret() values in console and persisted run output. A…
When was the CVE record for CVE-2026-119290 published?
The CVE record for CVE-2026-119290 was published on October 30, 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-119290 actively exploited?
CVE-2026-119290 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-119290?
CVE-2026-119290 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-119290?
A fix for CVE-2026-119290 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-119290

Explore →

Is Your Infrastructure Affected by CVE-2026-119290?

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