Skip to main content
CVE-2026-130589VulnerabilityPublished

Emitter through 3.1 contains a privilege escalation vulnerability that allows any channel key holder to forge a master

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130589· High 8.6

Not known to be exploited · CVSS 8.6 High.

Data as of 17 Nov 2026, 16:52 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.6
CNA (VulnCheck)CVSS 3.18.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
emitter-ioEmitterAffected
  • <=3.1
Fixed in–
GoEmitterpkg:golang/EmitterOther threatsAffected
  • <=3.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since the vulnerability arises from the lack of message authentication in the encryption scheme, mitigation would require implementing a cryptographically secure authenticated encryption mechanism (e.g., adding a MAC or signature) for channel keys. Until a fix is available, restrict access to channel keys and monitor for unauthorized key generation attempts.

Description

Emitter versions through 3.1 have a privilege escalation vulnerability due to insecure key encryption. Channel keys use XOR Salsa20 encryption without integrity protection, allowing any channel key holder to forge a master key by manipulating the permissions byte. This forged master key can then be used to generate keys with arbitrary permissions across all channels of the contract.

References

Community reviews

Loading reviews…