{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-57111 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-57111 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-57111 is a high-severity vulnerability in Apache Helix REST, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-57111 and fix it if it is affected.\n\nWhat it is: CVE-2026-57111 is a high-severity vulnerability in Apache Helix REST, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-57111 in the wild and no public exploit code.\n\nAffected product: Apache Helix REST. 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-57111/ (Markdown: https://insights.sbomify.com/CVE-2026-57111/index.md)","id":"CVE-2026-57111","markdown":"https://insights.sbomify.com/CVE-2026-57111/index.md","name":"CVE-2026-57111","record":{"aliases":["GHSA-2h97-jww5-mwvc"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Helix REST","requires_auth":"none","summary":"Permissive CORS settings in Apache Helix REST allow attackers to read data and modify state via cross-origin requests from malicious websites.","user_interaction":"not_required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"helix","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-1385","name":"Missing Origin Validation in WebSockets"}],"description":"Permissive Cross-Origin Resource Sharing (CORS) in the REST API (helix-rest, org.apache.helix.rest.server.filters.CORSFilter) in Apache Helix through 2.0.0 on all platforms allows a remote attacker controlling a web page visited by an authorized user to read responses from and issue cross-origin requests to administrative REST endpoints via a cross-origin request from an arbitrary origin, since the filter unconditionally returns Access-Control-Allow-Origin: * together with Access-Control-Allow-Credentials: true and reflects arbitrary Access-Control-Request-Method / Access-Control-Request-Headers values in preflight responses. Users are recommended to upgrade to version 2.0.1, which fixes this issue.","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":"Apache Helix REST: Permissive CORS Configuration in REST API Allows Unrestricted Cross-Origin","id":"CVE-2026-57111","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"PraisonAI ToolsMCPServer legacy SSE transport accepts attacker Host/Origin and exposes registered tools","id":"CVE-2026-57112"},"packages":[],"prev":{"headline":".NET Denial of Service Vulnerability","id":"CVE-2026-57108"},"products":["Apache Helix REST"],"published":"2026-07-09","related":[{"cvss_score":9.8,"headline":"Apache Helix: Deserialization vulnerability in Helix workflow and REST","id":"CVE-2023-38647","kev_date_added":null,"published":"2023-07-26"},{"cvss_score":7.5,"headline":"Apache Helix Front (UI): Helix front hard-coded secret in the express-session","id":"CVE-2024-22281","kev_date_added":null,"published":"2024-08-20"},{"cvss_score":6.1,"headline":"Apache Helix: Open redirect","id":"CVE-2022-47500","kev_date_added":null,"published":"2022-12-19"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["Apache Software Foundation"]},"summary":"Permissive CORS settings in Apache Helix REST allow attackers to read data and modify state via cross-origin requests from malicious websites.","url":"https://insights.sbomify.com/CVE-2026-57111/"}