# CVE-2026-108598: Floci 1.1.0 before 2.2.0 RCE via API Gateway VTL Mapping Templates

> Unauthenticated attackers can execute arbitrary OS commands in the Floci JVM by injecting malicious code into Velocity mapping templates.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-3p4c-wp7w-mgjx, GHSA-c3c4-9g85-pfvc

## What is CVE-2026-108598?

CVE-2026-108598 is a critical code injection vulnerability in floci-io floci, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Floci 1.1.0 before 2.2.0 contains a code injection vulnerability in VtlTemplateEngine that allows unauthenticated attackers to execute commands via unrestricted Velocity mapping templates. Attackers can create a REST API with a MOCK integration whose template uses $util reflection to reach Runtime or ProcessBuilder, executing OS commands in the Floci JVM.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-108598 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108598 exists.

Public exploit code:

- Unauthenticated RCE via Velocity Template Language (VTL) injection in Floci API Gateway mapping templates (versions 1.1.0–2.2.0). CVSS 9.8 Critical. (github_poc): https://github.com/Sidesploitx/CVE-2026-108598

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108598 is a critical code injection vulnerability in floci-io floci, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108598 exists.

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

## Sources

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

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