# CVE-2026-118477: KaliFast Project Management Platform ei_git_repo_url OS Command Injection


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-5r57-pmj5-8h6f

## What is CVE-2026-118477?

CVE-2026-118477 is a high-severity vulnerability in EISGE Kalifast, published on 28 Oct 2026. 

### Official description

The ei_git_repo_url parameter in the Git remote configuration endpoint of KaliFast is vulnerable to OS Command Injection. This OS Command Injection vulnerability allows an authenticated attacker (free registration available) to execute arbitrary commands on the KaliFast server with www-data privileges. Fixed in version 2026061802.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

No fix has been published for CVE-2026-118477 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118477 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118477 is a high-severity vulnerability in EISGE Kalifast, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118477 in the wild and no public exploit code.

Affected product: EISGE Kalifast. 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-118477/ (Markdown: https://insights.sbomify.com/CVE-2026-118477/index.md)
```

## Sources

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

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