CVE-2026-132756: geany · OS Command Injection
Affects geanySource CVE Database V5
Not known to be exploited · CVSS 8.5 High.
Data as of 18 Nov 2026, 23:35 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.5 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.8 |
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 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 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| geanygeany | Affected
| Fixed in– |
GitHubgeanypkg:github/geanyOther 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
Until a fix is available, users should avoid opening or building files with untrusted or suspicious filenames containing shell metacharacters in Geany.
Description
Geany versions up to 2.1.0 contain an OS command injection vulnerability. This flaw allows attackers to execute arbitrary shell commands by crafting filenames with special shell metacharacters such as backticks or $(...). When a user runs Compile, Build, or Execute commands on such files, the embedded commands execute with the user's privileges.
References
- github.com/geany/geany/issues/4611 (opens in a new tab)
- github.com/geany/geany/blob/2.1.0/src/utils.c (opens in a new tab)
- github.com/geany/geany/blob/2.1.0/src/build.c (opens in a new tab)
- vulncheck.com/advisories/geany-through-2.1.0-os-command-injection-via-filename-in-build-commands (opens in a new tab)