CVE-2026-34243 json
wenxian: Command Injection in GitHub Actions Workflow via `issue_comment.body`
published 2026-03-29 7 mo ago modified 2026-07-24 3 mo ago also EUVD-2026-17522 , GHSA-r4fj-r33x-8v88
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
wenxian is a tool to generate BIBTEX files from given identifiers (DOI, PMID, arXiv ID, or paper title). In versions 0.3.1 and prior, a GitHub Actions workflow uses untrusted user input from issue_comment.body directly inside a shell command, allowing potential command injection and arbitrary code execution on the runner. At time of publication, there are no publicly available patches.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 7 mo ago
Exploit prediction
2.21% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/njzjz/wenxian/security/advisories/GHSA-r4fj-r33x-8v88 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| github-actions | njzjz/wenxian | <=0.3.1 |
no fix listed |
Affected products
- njzjz wenxian
Classification
References
-
github.com
/njzjz/wenxian/security/advisories/GHSA-r4fj-r33x-8v88
web, exploit, mitigation, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-34243
advisory
-
github.com
/njzjz/wenxian
package
Sources
- CVE List CVE-2026-34243
- GitHub Advisory GHSA-r4fj-r33x-8v88
- NVD CVE-2026-34243
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.