# CVE-2026-24712: Command injection in n/a

> Attackers can execute arbitrary commands on systems running CFEngine Enterprise or Community, requiring an upgrade to patched versions.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 May 2026
- **Updated:** 15 May 2026
- **Also known as:** DEBIAN-CVE-2026-24712, GHSA-mcq4-jrhv-99mg, UBUNTU-CVE-2026-24712

## What is CVE-2026-24712?

CVE-2026-24712 is a high-severity command injection vulnerability in n/a, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Northern.tech CFEngine Enterprise and Community before 3.21.8, 3.24.3, and 3.27.0 allows Command injection.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-24712?

It affects 1 product.


Products: Northern.tech Cfengine.

## How do I fix CVE-2026-24712?

Upgrade to a fixed version.

## Is CVE-2026-24712 being exploited?

There is no known exploitation of CVE-2026-24712 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-45684](https://insights.sbomify.com/CVE-2023-45684/): SQL injection in n/a (high 7.5)
- [CVE-2023-26560](https://insights.sbomify.com/CVE-2023-26560/): Information disclosure in n/a (medium 6.5)
- [CVE-2021-36756](https://insights.sbomify.com/CVE-2021-36756/): Security feature bypass in n/a (medium 6.5)
- [CVE-2026-24710](https://insights.sbomify.com/CVE-2026-24710/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-19394](https://insights.sbomify.com/CVE-2019-19394/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24712 and fix it if it is affected.

What it is: CVE-2026-24712 is a high-severity command injection vulnerability in n/a, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24712 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24712/ (Markdown: https://insights.sbomify.com/CVE-2026-24712/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24712
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24712
- OSV: https://osv.dev/vulnerability/CVE-2026-24712

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24712/
Summaries are generated and may contain mistakes; the official description above is the record.