{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-2787 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-2787 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2787 is a high-severity code injection vulnerability in KNIME Business Hub, published on 26 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-2787 and fix it if it is affected.\n\nWhat it is: CVE-2025-2787 is a high-severity code injection vulnerability in KNIME Business Hub, published on 26 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-2787 in the wild and no public exploit code.\n\nAffected product: KNIME Business Hub. 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-2025-2787/ (Markdown: https://insights.sbomify.com/CVE-2025-2787/index.md)","id":"CVE-2025-2787","markdown":"https://insights.sbomify.com/CVE-2025-2787/index.md","name":"CVE-2025-2787","record":{"aliases":["GHSA-x237-489c-52j2"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"KNIME Business Hub","requires_auth":"low_privilege","summary":"An attacker with internal cluster access can exploit an ingress-nginx vulnerability to achieve complete Kubernetes cluster takeover.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"KNIME","cpe":[{"product":"business_hub","vendor":"knime"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/AU:N/R:U/V:C/RE:M/U:Amber","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"KNIME Business Hub is affected by the Ingress-nginx CVE-2025-1974 ( a.k.a IngressNightmare ) vulnerability which affects the ingress-nginx component. In the worst case a complete takeover of the Kubernetes cluster is possible. Since the affected component is only reachable from within the cluster, i.e. requires an authenticated user, the severity in the context of KNIME Business Hub is slightly lower.\n\nBesides applying the publicly known workarounds, we strongly recommend updating to one of the following versions of KNIME Business Hub: \n\n  *  1.13.3 or above \n\n  *  1.12.4 or above \n\n  *  1.11.4 or above \n\n  *  1.10.4 or above\n\n  *","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":"Ingress-nginx vulnerability in KNIME Business Hub","id":"CVE-2025-2787","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in MultiVendorX – WooCommerce Multivendor Marketplace Solutions","id":"CVE-2025-2789"},"packages":[],"prev":{"headline":"Tempo-operator: serviceaccount token exposure leading to token and subject access reviews in openshift tempo operator","id":"CVE-2025-2786"},"products":["KNIME Business Hub"],"published":"2025-03-26","related":[{"cvss_score":8.8,"headline":"Hard-coded password for object store of KNIME Business Hub","id":"CVE-2025-2402","kev_date_added":null,"published":"2025-03-31"},{"cvss_score":7.1,"headline":"Denial-of-service on KNIME Business Hub when certain jobs are executed","id":"CVE-2024-6598","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":5.3,"headline":"Jobs can be saved as workflows with wrong permissions on KNIME Business Hub","id":"CVE-2025-14262","kev_date_added":null,"published":"2025-12-08"},{"cvss_score":5.3,"headline":"Open redirect vulnerability in KNIME Business Hub","id":"CVE-2025-11240","kev_date_added":null,"published":"2025-10-02"},{"cvss_score":5.3,"headline":"Cross-site scripting vulnerabilities in KNIME Business Hub web pages","id":"CVE-2025-3019","kev_date_added":null,"published":"2025-03-31"},{"cvss_score":5.3,"headline":"Sensitive information disclosure in KNIME Hub Web Application","id":"CVE-2023-2541","kev_date_added":null,"published":"2023-06-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"total"},"state":"PUBLISHED","updated":"2025-04-08","vendors":["KNIME"]},"summary":"An attacker with internal cluster access can exploit an ingress-nginx vulnerability to achieve complete Kubernetes cluster takeover.","url":"https://insights.sbomify.com/CVE-2025-2787/"}