CVE-2026-54594

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% 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 weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OmniBlocks is a monorepo for the OmniBlocks project. Prior to the June 6, 2026 workflow remediation, .github/workflows/disc.yml runs for the issues opened event and the issues edited event and invokes the createDiscussion mutation whenever an issue is classified as off-topic, without recording that the issue was already converted or otherwise suppressing duplicate runs. A user who creates one off-topic issue and repeatedly edits its description before conversion completes can therefore cause multiple discussions to be created for the same issue, producing discussion spam and additional moderation work. This issue is fixed with commit 627e0f0a16a7d74b09128106b57dd7e85d2545df.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Sep 17, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit 627e0f0a16a7 (OmniBlocks/monorepo)

Fix landed in OmniBlocks/monorepo commit 627e0f0a16a7 — awaiting tagged release

https://github.com/OmniBlocks/monorepo/commit/627e0f0a16a7d74b09128106b57dd7e85d2545df
github_commit

commit 2953ef77649f (OmniBlocks/monorepo)

Fix landed in OmniBlocks/monorepo commit 2953ef77649f — awaiting tagged release

https://github.com/OmniBlocks/monorepo/commit/2953ef77649fc3c206fc1ee306f74cedc31b67e3
github Patch Available🟡 PoC Available

Spamming in Discussions tab possible via disc.yml · Advisory · OmniBlocks/monorepo · GitHub

https://github.com/OmniBlocks/monorepo/security/advisories/GHSA-pq9c-3595-72jq

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 6× 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-09-18 21:17 UTCEG score recompute
  2. 2026-09-18 20:34 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 20:18 UTCEG score recompute
  5. 2026-09-17 19:54 UTCEG score recompute
  6. 2026-09-17 19:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54594?
CVE-2026-54594 is a medium vulnerability published on September 17, 2026. OmniBlocks is a monorepo for the OmniBlocks project. Prior to the June 6, 2026 workflow remediation, .github/workflows/disc.yml runs for the issues opened event and the issues edited event and invokes the createDiscussion mutation whenever an issue is classified as off-topic, without recording that…
When was CVE-2026-54594 disclosed?
CVE-2026-54594 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54594 actively exploited?
CVE-2026-54594 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 73.6% of all scored CVEs.
What is the CVSS score of CVE-2026-54594?
CVE-2026-54594 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-54594?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54594, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54594?

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

Start Free Scan →Browse All CVEs