# CVE-2026-54594: OmniBlocks: Spamming in Discussions tab possible via disc.yml

> Attackers can spam discussions by repeatedly editing off-topic issues, causing duplicate discussion creation in OmniBlocks workflows.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-pq9c-3595-72jq

## What is CVE-2026-54594?

CVE-2026-54594 is a medium-severity vulnerability in OmniBlocks monorepo, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-799 (Improper Control of Interaction Frequency)

## Which versions are affected by CVE-2026-54594?


## How do I fix CVE-2026-54594?

No fix has been published for CVE-2026-54594 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54594 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54594 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54594 and fix it if it is affected.

What it is: CVE-2026-54594 is a medium-severity vulnerability in OmniBlocks monorepo, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54594 exists.

Affected product: OmniBlocks monorepo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54594/ (Markdown: https://insights.sbomify.com/CVE-2026-54594/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54594
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54594
- OSV: https://osv.dev/vulnerability/CVE-2026-54594

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54594/
Summaries are generated and may contain mistakes; the official description above is the record.