CVE-2026-76761: chenhg5 cc-connect · OS Command Injection
Affects chenhg5 cc-connectSource CVE Database V5
Public exploit available · CVSS 6.9 Medium.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 2.1% chance of exploitation in 30 days – higher than 82% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| chenhg5cc-connect | Affected
| Fixed in– |
Gogithub.com/chenhg5/cc-connectpkg:golang/github.com/chenhg5/cc-connectOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:chenhg5:cc-connect:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, restrict access to the Management API and monitor for suspicious activity related to command execution attempts. Avoid exposing vulnerable versions to untrusted networks.
Description
CVE-2026-76761 is an OS command injection vulnerability in chenhg5 cc-connect versions 1.4.0 and 1.4.1. It affects the shellExecCommand function in the core/engine.go file of the Management API component. The vulnerability allows remote attackers to manipulate the exec argument to execute arbitrary OS commands. Exploit code is publicly available, but there is no indication of active exploitation in the wild. The issue was reported but the related GitHub issue was closed due to inactivity.