{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41177 exists.","fix":"No fix has been published for CVE-2026-41177 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41177 is a medium-severity server-side request forgery vulnerability in squidex, published on 22 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41177 and fix it if it is affected.\n\nWhat it is: CVE-2026-41177 is a medium-severity server-side request forgery vulnerability in squidex, published on 22 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41177 exists.\n\nAffected product: squidex. 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-41177/ (Markdown: https://insights.sbomify.com/CVE-2026-41177/index.md)","id":"CVE-2026-41177","markdown":"https://insights.sbomify.com/CVE-2026-41177/index.md","name":"CVE-2026-41177","record":{"aliases":["GHSA-45fq-w37p-qfw5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Headless CMS","requires_auth":"high_privilege","summary":"An authenticated administrator can exploit Blind SSRF via the file:// protocol in the Restore API to interact with the local filesystem and disclose sensitive information.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-73","name":"External Control of File Name or Path"}],"description":"Squidex is an open source headless content management system and content management hub. Prior to version 7.23.0, the Squidex Restore API is vulnerable to Blind Server-Side Request Forgery (SSRF). The application fails to validate the URI scheme of the user-supplied `Url` parameter, allowing the use of the `file://` protocol. This allows an authenticated administrator to force the backend server to interact with the local filesystem, which can lead to Local File Interaction (LFI) and potential disclosure of sensitive system information through side-channel analysis of internal logs. Version 7.23.0 contains a fix.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-04-25","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-04-25T20:50:18Z","kind":"github_poc","ref":"https://github.com/TurkiOS/CVE-2026-41177-Squidex-CMS","stars":0,"title":"CVE-2026-41177, a Blind SSRF vulnerability in Squidex CMS (prior to v7.23.0). Includes root cause analysis, reproduction steps, and impact assessment regarding Local File Interaction (LFI)."}],"tier":"weaponised"},"has_fix":false,"headline":"Squidex has Blind SSRF via file:// Protocol in Restore API leading to Local File Interaction","id":"CVE-2026-41177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"OpenTelemetry-Go's baggage parsing no longer caps raw header length","id":"CVE-2026-41178"},"packages":[],"prev":{"headline":"Rclone: Unauthenticated options/set allows runtime auth bypass, leading to sensitive operations and command execution","id":"CVE-2026-41176"},"products":["squidex"],"published":"2026-04-22","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-23","vendors":["Squidex"]},"summary":"An authenticated administrator can exploit Blind SSRF via the file:// protocol in the Restore API to interact with the local filesystem and disclose sensitive information.","url":"https://insights.sbomify.com/CVE-2026-41177/"}