Skip to content
High-Priority CVE-2026-130589 Discovered in Emitter-io

High-Priority CVE-2026-130589 Discovered in Emitter-io

First seen 17 Nov 2026, 16:12 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 17, 2026 at 16:12 UTC
  • •CVE-2026-130589 allows privilege escalation via forged master keys.
  • •Affected versions include Emitter up to 3.1; risk is high for exposed deployments.
  • •No active exploitation confirmed, but significant risks to data integrity exist.

A privilege escalation vulnerability (CVE-2026-130589) has been identified in Emitter versions up to 3.1, allowing any channel key holder to forge a master key. The flaw arises from the use of bare XOR Salsa20 encryption without a MAC or signature, enabling attackers to modify permissions and mint keys with arbitrary access. The risk is classified as high-priority due to potential unauthorized access to sensitive channel data and manipulation of permissions. Active exploitation has not been confirmed, but the vulnerability poses significant risks to confidentiality and integrity. Users with valid channel keys are most exposed, particularly in internet-accessible deployments. Mitigation steps include restricting key-generation access and reviewing permissions and activity logs. The CVE was published on November 17, 2026, with a CVSS score of 8.6.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-02
Vulnerability reported to VulnCheck
The issue was submitted for coordinated vulnerability disclosure and validated as CVE-eligible.
github.com
2026-11-17
CVE-2026-130589 published
The vulnerability was officially published with a CVSS score of 8.6, marking it as high priority.
Redpacketsecurity

More articles in this cluster (6)

Following this threat?

Track CVE-2026-130589 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

What versions of Emitter are affected?
Emitter versions up to 3.1 are affected by CVE-2026-130589.
Is there any active exploitation of this vulnerability?
No active exploitation has been confirmed at this time.
What immediate actions should be taken?
Restrict key-generation access and review permissions and activity logs for unusual changes.