CVE-2026-71551Public exploit

Arbitrary command execution via renderer IPC exec

Published Aug 18, 2026 · Updated Aug 21, 2026

Command injection in Super Productivity before 18.13.0 allows attackers to execute OS commands via renderer-supplied IPC EXEC input. The electron/ipc-handlers/exec.ts handler forwards command strings from window.ea.exec() to child_process.exec(), so renderer code and community plugins can reach a system shell, and accepted commands are persisted in ALLOWED_COMMANDS for later silent reuse. Exploitation requires local user interaction to install or enable a malicious plugin and approve its first command, after which the desktop account's privileges are available to that plugin or any other code that reuses the whitelisted command.

CVSS severity7.8
High
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Command injection in Super Productivity before 18.13.0 allows attackers to execute OS commands via renderer-supplied IPC EXEC input. The electron/ipc-handlers/exec.ts handler forwards command strings from window.ea.exec() to child_process.exec(), so renderer code and community plugins can reach a system shell, and accepted commands are persisted in ALLOWED_COMMANDS for later silent reuse. Exploitation requires local user interaction to install or enable a malicious plugin and approve its first command, after which the desktop account's privileges are available to that plugin or any other code that reuses the whitelisted command.

The record

CVE
CVE-2026-71551
Published
Aug 18, 2026
Updated
Aug 21, 2026
Vendor
Super Productivity
Product
Super Productivity
Classifications
CWE-78, T1059
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 21, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 18.13.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

Super Productivity · Super Productivityversion=< 18.13.0

Published CVSS scores

7.8GitHub, Inc.CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
T1059Command and Scripting Interpreter

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo