{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119711 exists.","exposure":"","fix":"No fix has been published for CVE-2026-119711 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119711 is a medium-severity vulnerability in pipeshub-ai, published on 30 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119711 and fix it if it is affected.\n\nWhat it is: CVE-2026-119711 is a medium-severity vulnerability in pipeshub-ai, published on 30 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119711 exists.\n\nAffected product: pipeshub-ai. 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-119711/ (Markdown: https://insights.sbomify.com/CVE-2026-119711/index.md)","id":"CVE-2026-119711","markdown":"https://insights.sbomify.com/CVE-2026-119711/index.md","name":"CVE-2026-119711","record":{"aliases":["GHSA-78gw-g2h7-xvjj","GHSA-v4v4-55gm-p3cp"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-348","name":"Use of Less Trusted Source"}],"description":"PipesHub before 0.10.0 contains a rate limit bypass vulnerability in getClientIp() that allows unauthenticated attackers to evade per-IP throttling by spoofing X-Forwarded-For or X-Real-IP headers. Attackers can rotate header values to obtain fresh rate-limit buckets on authentication endpoints, enabling password spraying and OTP or password-reset email flooding.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"PipesHub before 0.10.0 Rate Limit Bypass via Spoofed X-Forwarded-For Header","id":"CVE-2026-119711","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"PipesHub before 0.10.0 SSRF via Image URLs in Indexed Documents","id":"CVE-2026-119712"},"nickname":null,"packages":[],"prev":{"headline":"PipesHub 0.3.0 before 0.10.0 Connector Deletion via Crawling-Manager Schedule Route","id":"CVE-2026-119710"},"products":["pipeshub-ai"],"published":"2026-10-30","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-04","vendors":["pipeshub-ai"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119711/"}