# CVE-2026-130589: Emitter through 3.1 Master Key Forgery via Unauthenticated Channel Key Encryption


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-f5vm-843q-8fq7

## What is CVE-2026-130589?

CVE-2026-130589 is a high-severity vulnerability in emitter-io Emitter, published on 17 Nov 2026. 

### Official description

Emitter through 3.1 contains a privilege escalation vulnerability that allows any channel key holder to forge a master key because channel keys use bare XOR Salsa20 encryption without a MAC or signature. Attackers can flip the permissions byte to the master value and present the forged key to the keygen service to mint keys with arbitrary permissions on every channel of the contract.

Weakness: CWE-649 (Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking)

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

1 open source package ship an affected version, including github.com/emitter-io/emitter.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `github.com/emitter-io/emitter` | Go | `pkg:golang/github.com/emitter-io/emitter` | All versions to 3.1 | None |

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

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

## Is CVE-2026-130589 being exploited?

There is no known exploitation of CVE-2026-130589 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130589 is a high-severity vulnerability in emitter-io Emitter, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130589 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/emitter-io/emitter (Go): affected all versions up to 3.1; no fix listed

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-130589/ (Markdown: https://insights.sbomify.com/CVE-2026-130589/index.md)
```

## Sources

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

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