CVE-2026-40042: pancho Pachno · File Descriptor Leak
Affects pancho PachnoSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical.
Data as of 29 Oct 2026, 19:04 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% 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:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PachnoPachno | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, users should consider disabling or restricting XML parsing features that use simplexml_load_string() without LIBXML_NONET or apply custom input validation to block malicious XML entities. Monitor vendor channels for updates and apply patches promptly once released.
Description
Pachno version 1.0.6 contains a critical XML external entity (XXE) injection vulnerability. This flaw allows unauthenticated attackers to read arbitrary files by exploiting unsafe XML parsing in the TextParser helper component. The vulnerability arises from the use of simplexml_load_string() without disabling network access (LIBXML_NONET), enabling malicious XML entities injected via wiki table syntax and inline tags in issue descriptions, comments, and wiki articles to be resolved. The vulnerability has a CVSS 4.0 score of 9.3, indicating critical severity. No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.