{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-113619 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-113619 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-113619 is a high-severity vulnerability in Eclipse ioFog, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-113619 and fix it if it is affected.\n\nWhat it is: CVE-2026-113619 is a high-severity vulnerability in Eclipse ioFog, published on 20 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-113619 in the wild and no public exploit code.\n\nAffected product: Eclipse ioFog. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-113619/ (Markdown: https://insights.sbomify.com/CVE-2026-113619/index.md)","id":"CVE-2026-113619","markdown":"https://insights.sbomify.com/CVE-2026-113619/index.md","name":"CVE-2026-113619","record":{"aliases":["GHSA-w6hw-cr6m-h7xj"],"analysis":null,"analysis_generated_by":null,"assigner":"eclipse","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Eclipse ioFog renders request templates before authentication","id":"CVE-2026-113619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Eclipse ioFog operator WebSocket accepts an unverified JWT","id":"CVE-2026-113620"},"packages":[],"prev":{"headline":"Automated Import Products to Cart \u003c 1.0.4 - Subscriber+ Arbitrary File Read and Deletion via Path Traversal","id":"CVE-2026-113617"},"products":["Eclipse ioFog"],"published":"2026-10-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["Eclipse Foundation"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-113619/"}