CVE
Geany OS command injection via filenames in build commands
Affects Geany through 2.1.0 on Unix platforms such as Linux and macOS when Compile, Build or Execute commands substitute the filename. No fixed version is listed in the checked facts.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Geany through 2.1.0 Unix platforms such as Linux and macOS Build, Compile or Execute commands that substitute the filename, run through /bin/sh
Summary
Geany, a text editor, is affected by an OS command injection flaw in its build and execute commands. A local attacker who plants a file with shell metacharacters such as backticks or $(...) in its name can run arbitrary commands as the user when someone runs Compile, Build or Execute on that file.
Original description
Geany through 2.1.0 contains an OS command injection vulnerability that allows attackers to run shell commands by embedding metacharacters in filenames substituted into build and execute commands. Attackers can craft a file named with backticks or $(...) that executes via /bin/sh when a user runs Compile, Build or Execute, gaining code execution as the user.
Who should check
Geany users on Linux or macOS running Geany through 2.1.0 with build, compile or execute commands
“Geany through 2.1.0 contains an OS command injection vulnerability”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch5/5No patch listed yet
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Geany through 2.1.0 Unix platforms such as Linux and macOS Build, Compile or Execute commands that substitute the filename, run through /bin/shWorkaround: Until a fix is available, avoid using Compile, Build or Execute commands that substitute the filename. This limits the affected feature; the checked facts list no other workaround.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132756 (Geany through 2.1.0 OS Command Injection via Filename in Build Commands), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132756 (entry last updated 2026-11-18):
Affected:
- geany geany: through 2.1.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Geany through 2.1.0 (source: https://www.vulncheck.com/advisories/geany-through-2.1.0-os-command-injection-via-filename-in-build-commands)
- Unix platforms such as Linux and macOS (source: https://github.com/geany/geany/issues/4611)
- Build, Compile or Execute commands that substitute the filename, run through /bin/sh (source: https://www.vulncheck.com/advisories/geany-through-2.1.0-os-command-injection-via-filename-in-build-commands)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-132756 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132756 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/geany/geany/issues/4611
- https://github.com/geany/geany/blob/2.1.0/src/utils.c#L2561-L2610
- https://github.com/geany/geany/blob/2.1.0/src/build.c#L1100-L1111
- https://www.vulncheck.com/advisories/geany-through-2.1.0-os-command-injection-via-filename-in-build-commands
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132756
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132756"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- geany geany
through 2.1.0
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132756 |
| Record | NVD · CVE-2026-132756 |
| Other links 4 | |
| Report | GitHub · geany/geany · Issue #4611 |
| Repository | GitHub · geany/geany · src/utils.c · L2561-L2610 |
| Repository | GitHub · geany/geany · src/build.c · L1100-L1111 |
| Link | vulncheck.com · advisories/geany-through-2.1.0-os-command-injection-via-filename-in-build-commands |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132756
Is CVE-2026-132756 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Build, Compile or Execute commands that substitute the filename are run through /bin/sh, so a filename can inject OS commands. The injected commands run with the victim's user privileges.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-132756?
geany: through 2.1.0.Source: cve.now feed data
Am I affected, and how do I check?
Geany through 2.1.0 on Unix platforms such as Linux and macOS is affected when build commands substitute the filename. To check, run geany --version and look at the build command settings for any filename substitution.Source: vulncheck.com, github.com
How do I fix CVE-2026-132756?
The checked facts do not list a fixed version or vendor patch ids. Check the Geany project's advisory or release notes for a patched release and upgrade when one is available.Source: vulncheck.com, github.com
What if there's no patch?
Until a fix is available, avoid using Compile, Build or Execute commands that substitute the filename. This limits the affected feature; the checked facts list no other workaround.Source: vulncheck.com, github.com