CVE
Emitter privilege escalation via forged master key in keygen
Affects Emitter 3.1 and earlier, where a channel key holder can forge a master key. CVSS scores it 8.6 (high); no vendor rating or fixed version is given.
Written by a model from the sources below. Verify against them.
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
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Emitter version 3.1 or earlier (through 3.1). Attacker must already hold a valid channel key.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 32/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Emitter from emitter-io has a privilege escalation flaw that lets an attacker who holds a channel key forge a master key. The attacker can then use that key with the keygen service to create keys with arbitrary permissions on every channel in the contract. The attack can be carried out remotely with only a low-privilege channel key.
Original 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.
Who should check
Teams running emitter-io Emitter (Go) through 3.1 that issue or distribute channel keys.
“Affecting Emitter <= 3.1”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity8.6/10CVSS 8.6
- No patch5/5No patch listed yet
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 39 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Emitter version 3.1 or earlier (through 3.1). Attacker must already hold a valid channel key.Workaround: The checked facts give no vendor workaround. Because the attack requires a valid channel key, limiting who holds channel keys is the only restriction the facts support.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130589 (Emitter through 3.1 Master Key Forgery via Unauthenticated Channel Key Encryption), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130589 (entry last updated 2026-11-17):
Affected:
- Go package github.com/emitter-io/emitter: through 3.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Emitter version 3.1 or earlier (through 3.1). (source: https://www.vulncheck.com/advisories/emitter-through-3.1-master-key-forgery-via-unauthenticated-channel-key-encryption)
- Attacker must already hold a valid channel key. (source: https://www.vulncheck.com/advisories/emitter-through-3.1-master-key-forgery-via-unauthenticated-channel-key-encryption)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130589 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130589 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/emitter-io/emitter/issues/439
- https://github.com/emitter-io/emitter/blob/v3.1/internal/security/cipher/shuffle.go#L75-L90
- https://github.com/emitter-io/emitter/blob/v3.1/internal/provider/contract/contract.go#L57-L62
- https://github.com/emitter-io/emitter/blob/v3.1/internal/service/keygen/keygen.go#L65
- https://www.vulncheck.com/advisories/emitter-through-3.1-master-key-forgery-via-unauthenticated-channel-key-encryption
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130589
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130589"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
through 3.1
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Report
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130589
Is CVE-2026-130589 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A holder of a valid channel key can forge a master key. The forged key can then mint keys with arbitrary permissions on every channel of the contract.Source: vulncheck.com
Which versions are affected by CVE-2026-130589?
github.com/emitter-io/emitter (Go): through 3.1.Source: cve.now feed data
Am I affected, and how do I check?
Emitter version 3.1 or earlier (through 3.1) is affected, and the attacker must already hold a valid channel key. Check the installed Emitter version against 3.1 to see where it falls.Source: vulncheck.com
How do I fix CVE-2026-130589?
The checked facts name no fixed version or vendor patch, so no upgrade target can be given. Check the vendor's advisory for a fix.Source: vulncheck.com
What if there's no patch?
The checked facts give no vendor workaround. Because the attack requires a valid channel key, limiting who holds channel keys is the only restriction the facts support.Source: vulncheck.com