{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-110726 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-110726 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-110726 is a medium-severity vulnerability in Eclipse Connected Services Platform, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-110726 and fix it if it is affected.\n\nWhat it is: CVE-2026-110726 is a medium-severity vulnerability in Eclipse Connected Services Platform, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-110726 in the wild and no public exploit code.\n\nAffected product: Eclipse Connected Services Platform. 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-110726/ (Markdown: https://insights.sbomify.com/CVE-2026-110726/index.md)","id":"CVE-2026-110726","markdown":"https://insights.sbomify.com/CVE-2026-110726/index.md","name":"CVE-2026-110726","record":{"aliases":["GHSA-ch6x-rg7q-7jfx","GHSA-r566-6hq2-633r"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Eclipse API Gateway","requires_auth":"low_privilege","summary":"Attackers can bypass rate limiting in Eclipse API Gateway by spoofing the X-Forwarded-For header, allowing unlimited requests per route.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-807","name":"Reliance on Untrusted Inputs in a Security Decision"},{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-348","name":"Use of Less Trusted Source"}],"description":"In `api-gateway` versions till `1.7.3`, The default rate-limit key resolver, `ClientIpKeyResolver`, derives the per-client bucket key from the leftmost element of the `X-Forwarded-For` request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy list. A single attacker can therefore obtain an unlimited number of independent rate-limit buckets — one per unique header value — and completely bypass the gateway's request-rate limiting on every route that uses the shipped default configuration.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Security feature bypass in Eclipse Connected Services Platform","id":"CVE-2026-110726","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Apache SIS: SQL injection via unvalidated ORDER BY sort expression in the SQL feature store","id":"CVE-2026-110733"},"packages":[],"prev":{"headline":"fast-uri vulnerable to scheme injection via an unescaped first-segment colon in suffix references","id":"CVE-2026-110725"},"products":["Eclipse Connected Services Platform"],"published":"2026-10-15","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Eclipse Foundation"]},"summary":"Attackers can bypass rate limiting in Eclipse API Gateway by spoofing the X-Forwarded-For header, allowing unlimited requests per route.","url":"https://insights.sbomify.com/CVE-2026-110726/"}