# CVE-2026-113619: Eclipse ioFog renders request templates before authentication


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-w6hw-cr6m-h7xj

## What is CVE-2026-113619?

CVE-2026-113619 is a high-severity vulnerability in Eclipse ioFog, published on 20 Oct 2026. 

### Official description

In Eclipse ioFog Controller versions 3.8.0 through 3.9.1, POST, PUT, and PATCH bodies on routes that enable template substitution are rendered by an uncapped Liquid engine before authentication and RBAC. The bearer check does not reject a missing or invalid token, and the auth rate limit applies only to user login routes. A small JSON body can stall or abort the Controller process. The anonymous caller does not receive the rendered result; the impact is availability of the control plane, including the agent API and in-process WebSocket relays on that process.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-113619 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113619 is a high-severity vulnerability in Eclipse ioFog, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113619 in the wild and no public exploit code.

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

## Sources

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

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