Back Redpacketsecurity CVE Alert: CVE-2026-130589 – emitter-io
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.
**Risk verdict:** High-priority for exposed deployments: a user who already holds a channel key may be able to escalate privileges across the contract, but active exploitation is not established by the supplied data.
**Why this matters:** Successful abuse could grant access to sensitive channel data and permit unauthorised changes to channel permissions or content. This creates risks to confidentiality and integrity, including data exposure and manipulation; availability impact appears less likely. KEV status, SSVC exploitation state, PoC availability and EPSS are not provided, so exploitation likelihood cannot be confidently ranked.
**Most likely attack path:** An attacker needs network access to the key-generation service and a valid channel key, but no user interaction or complex setup. They can alter the key’s permissions and submit it to obtain elevated credentials; the stated scope is unchanged, though access may extend across channels within the same contract.
**Who is most exposed:** Prioritise internet-accessible or broadly reachable deployments of real-time messaging infrastructure, especially where channel keys are issued to users or services with limited trust.
Review key-generation logs for unexpected privilege levels or unusual issuance bursts.
Alert on permission changes spanning multiple channels or contracts.
Correlate new elevated keys with the same client, account or source address.
Investigate channel access or content changes immediately following key issuance.
Mitigation and prioritisation:
Confirm whether affected releases are deployed; obtain vendor remediation guidance before setting a patch target.
Restrict key-generation access to trusted networks and minimise channel-key distribution.
Rotate potentially exposed keys and review permissions and activity across affected contracts.
Test remediation in staging, then deploy promptly through change control; verify key integrity is enforced.
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
