CVE-2026-29811: cyberpanel
Affects cyberpanelSource CVE Database V5
Not known to be exploited : upgrade to 2.4.4 soon.
Data as of 26 Oct 2026, 14:05 UTC
Rated High by the CNA (mitre) · No CVSS score from NVD or the CNA
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.4.4
Exploitation evidence
Disclosed: evidence found.
CVE published 13 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade usmannasir/cyberpanel to 2.4.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubusmannasir/cyberpanelpkg:github/usmannasir/cyberpanelOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade CyberPanel to version 2.4.4 or later where this issue is addressed. Patch status is confirmed by the presence of affected versions being prior to 2.4.4, indicating that 2.4.4 contains the fix.
Description
CyberPanel versions prior to 2.4.4 contain a flaw in how they detect alias domains. Instead of using a proper Python conditional statement, the detection relies on an ORM query filter, which may lead to incorrect identification of alias domains.