Skip to main content

cc-connect EUVDEUVD-2026-96344

| CVE-2026-108549 CRITICAL
Missing Authentication for Critical Function (CWE-306)
2026-10-10 VulnCheck GHSA-h8j8-r6g6-37hc
9.2
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach webhook listener on port 8080
  2. Delivery
    Forge MAX update with admin user_id
  3. Exploit
    Bypass missing authentication check
  4. Execution
    Submit privileged /shell command
  5. Impact
    Execute arbitrary commands on host

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitable only when the MAX platform adapter is deployed in webhook mode AND no webhook_secret is configured, with the webhook listener on port 8080 reachable by the attacker; the attacker must also supply a valid allowed or admin user_id to invoke privileged commands like /shell. Limiting factors: configuring a webhook_secret closes the hole entirely, the listener must be network-reachable (not firewalled/bound to localhost), and knowledge of a permitted user_id is required - reflected by the CVSS 4.0 AC:H and AT:P metrics. This is a non-default-hardening/misconfiguration-dependent path rather than exploitation of a hardened default.

Impact

This is a genuinely high-priority flaw where exploitable, but its real-world reach is narrowed by configuration preconditions. The provided CVSS 4.0 vector (AV:N/PR:N/UI:N) confirms a network-reachable, unauthenticated attack path with full high impact to confidentiality, integrity and availability (VC:H/VI:H/VA:H) - consistent with CWE-306 (Missing Authentication) leading to arbitrary command execution via /shell on the host. However, two metrics temper the raw 9.2 score: AC:H and AT:P indicate the attack is not trivially universal - it depends on a specific deployment state (no webhook_secret configured) and on the attacker supplying a valid allowed/admin user_id. No EPSS score, CISA KEV listing, or public POC is present in the supplied data, so there is no evidence of active exploitation or widespread automation; exploitation status is best characterized as theoretical at analysis time. The dominant risk driver is therefore impact severity plus unauthenticated network exposure, offset by the fact that it only applies to misconfigured/default-secretless instances of a low-footprint open-source tool. Net: treat as critical-to-patch for any operator running the MAX adapter in webhook mode, but it is not a mass-exploitation Internet emergency on the evidence provided.

Exploit ScenarioDerived

An operator runs cc-connect's MAX platform adapter in webhook mode on port 8080 without setting webhook_secret. A remote attacker who can reach that listener crafts a forged MAX update containing an allowed or admin user_id and issues a privileged command such as /shell, achieving command execution on the host. No public exploit code is identified at time of analysis, and the AC:H/AT:P metrics mean the attacker needs the secret to be unset and must supply a valid privileged user_id.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 10, 2026

Missing authentication in the MAX platform adapter of cc-connect through 1.5.0 allows remote attackers to forge webhook updates and, by supplying an allowed or admin user_id, trigger privileged host commands such as /shell. The flaw only materialises when the MAX adapter is deployed in webhook mode with no webhook_secret configured and its listener on port 8080 is network-reachable; configuring a secret eliminates the exposure entirely. At time of analysis there is no CISA KEV entry, no vendor-released patch version published, and no public exploit identified, though the technical bar to exploitation is low once the misconfiguration is present.

RemediationAI

No vendor-released patch version was identified at time of analysis; the public GitHub issue chenhg5/cc-connect#1968 and the source reference at platform/max/max.go lines 287-305 are the available tracking artefacts, so the primary action is to configure a webhook_secret - an independent assessment confirms that setting one closes the hole entirely by forcing signature validation on inbound updates. The trade-off is operational: the same secret must be provisioned on the MAX sender side and rotated on a schedule, and any sender that cannot sign will stop delivering updates. Until a fixed release is available and deployed, restrict the port 8080 webhook listener so it is reachable only from the MAX platform's legitimate source addresses or bound to localhost behind a reverse proxy, accepting that this breaks delivery from any sender outside the allow-list. Additionally, remove or disable the /shell command from the allowed command set where it is not operationally required - this reduces post-exploitation impact but removes legitimate remote administration functionality - and avoid granting admin user_ids to accounts that do not strictly need them, since knowledge of a permitted user_id is a precondition for exploitation. Review adapter logs for webhook requests originating from unexpected source addresses or carrying surprising user_id values, and rotate any credentials or secrets reachable from the host if a forged /shell invocation is suspected. Monitor the project repository and the VulnCheck advisory for a patched release, and upgrade as soon as a version above 1.5.0 is published.

Affected VersionsENISA

cc-connect 0 ≤1.5.0

Affected Packages

euvd cc_connect no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The issue is a CWE-306 missing authentication for critical function in cc-connect, a Go-based connector that bridges chat platforms to host-side command execution. The vulnerable code path lives in platform/max/max.go (referenced lines 287-305 in the v1.5.0 source), where the MAX platform adapter accepts incoming webhook payloads in webhook mode. When no webhook_secret is configured, the handler performs no signature or shared-secret validation, so it treats any inbound HTTP request as a legitimate platform update. The attacker-controlled payload carries a user_id field, and the adapter trusts that field for authorisation decisions - meaning a forged request claiming an allowed or admin identity is treated as that user, granting access to privileged bot commands including /shell, which executes on the host. The affected CPE cpe:2.3:a:chenhg5:cc-connect:*:*:*:*:*:*:*:* indicates the vendor's entire tracked version range up to and including 1.5.0, and VulnCheck classifies the weakness as an authentication bypass via MAX webhook sender spoofing. The vendor's own CVSS 4.0 vector (AV:N/AC:H/AT:P/PR:N/UI:N) and our independent CVSS 3.1 assessment (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) agree on unauthenticated network reachability with full confidentiality, integrity and availability impact, while the High attack complexity and Present attack-requirements metrics reflect the configuration preconditions rather than any cryptographic barrier.

Know when Cc Connect gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 9.2 CRITICAL
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.1 HIGH

Network-reachable and unauthenticated (AV:N/PR:N), but AC:H because exploitation requires webhook_secret unset plus a valid privileged user_id; command execution yields full C/I/A with no scope change.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
High
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

cc-connect through 1.5.0 contains a missing authentication vulnerability in the MAX platform adapter webhook mode in platform/max/max.go that accepts unauthenticated updates when no webhook_secret is configured. Remote attackers reaching the webhook listener on port 8080 can forge updates with an allowed or admin user_id to run privileged commands like /shell on the host.

Executive ViewAI

Why It Matters

A critical authentication gap in the MAX platform adapter of cc-connect (all versions through 1.5.0) could allow an attacker to forge webhook traffic and execute privileged host commands such as /shell, but only where the adapter runs in webhook mode with no webhook_secret configured and its port 8080 listener is reachable from the network. No vendor patch has been published, so teams running that configuration cannot remediate by upgrading and must instead close the exposure through configuration change or network isolation. Because the misconfiguration is common in quick deployments and the affected component may sit on internet-facing infrastructure, leadership should treat this as an urgent, owner-assigned containment item rather than a routine patch cycle item.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations are configuration-based. Configure a webhook_secret (vendor states this eliminates the exposure entirely) or switch the MAX adapter out of webhook mode; block all network access to the port 8080 listener from untrusted networks (host firewall, security groups, VPN-only or authenticated reverse proxy); run the adapter as a low-privilege service account or in an isolated container to limit host command execution; monitor adapter and host logs for forged webhooks and privileged command activity.

Threat Intelligence Overview

EPSS Score
0.5%
Top 63% exploitable
Prevalence
Rare
obscure individual-maintained open-source connector, tiny production footprint
Social Media
4
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy