{"answers":{"affected":"1 open source package ship an affected version, including appsmith. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55455 exists.","fix":"Upgrade appsmith to 2.1.0 or later.","what":"CVE-2026-55455 is a medium-severity server-side request forgery vulnerability in appsmithorg appsmith, published on 24 Jun 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-55455 and fix it if it is affected.\n\nWhat it is: CVE-2026-55455 is a medium-severity server-side request forgery vulnerability in appsmithorg appsmith, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55455 exists.\n\nAffected packages and fixed versions:\n- appsmith (Bitnami): affected all versions; fixed in 2.1.0\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-55455/ (Markdown: https://insights.sbomify.com/CVE-2026-55455/index.md)","id":"CVE-2026-55455","markdown":"https://insights.sbomify.com/CVE-2026-55455/index.md","name":"CVE-2026-55455","record":{"aliases":["BIT-appsmith-2026-55455","GHSA-m23h-pvf3-2m7p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Appsmith platform","requires_auth":"low_privilege","summary":"Authenticated users can bypass host restrictions to access internal loopback services via REST or GraphQL plugins.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"appsmith","vendor":"appsmith"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Appsmith is a platform to build admin panels, internal tools, and dashboards. Prior to 2.1, the outbound HTTP host filter applied by WebClientUtils (used by the REST API and GraphQL datasource plugins) validates hosts against an exact-match string denylist. The comprehensive address-class check (loopback, any-local, link-local, fc00::/7) exists only on a separate code path used by SMTP, not by the HTTP plugin path. As a result, an authenticated user can craft outbound requests that reach loopback-bound services inside the container. This vulnerability is fixed in 2.1.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Appsmith: SSRF in REST API / GraphQL datasource plugins via insufficient host denylist","id":"CVE-2026-55455","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":1,"n_references":1,"next":{"headline":"This CVE is a duplicate of another CVE.","id":"CVE-2026-55456"},"packages":[{"ecosystem":"Bitnami","fixed":["2.1.0"],"introduced":["0"],"last_affected":[],"package":"appsmith","purl":"pkg:bitnami/appsmith","source":"BIT-appsmith-2026-55455"}],"prev":{"headline":"Appsmith: Caddy admin API exposed without authentication","id":"CVE-2026-55454"},"products":["appsmith"],"published":"2026-06-24","related":[{"cvss_score":9.9,"headline":"Appsmith: Caddy admin API exposed without authentication","id":"CVE-2026-55454","kev_date_added":null,"published":"2026-06-24"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2024-55964","kev_date_added":null,"published":"2025-03-26"},{"cvss_score":9.7,"headline":"Account Takeover Vulnerability in Appsmith","id":"CVE-2026-22794","kev_date_added":null,"published":"2026-01-12"},{"cvss_score":9.4,"headline":"Appsmith public apps can execute unpublished actions (viewMode confusion)","id":"CVE-2026-24042","kev_date_added":null,"published":"2026-01-22"},{"cvss_score":9.1,"headline":"Critical Stored XSS \u0026 Privilege Escalation in Appsmith","id":"CVE-2026-30862","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":8.9,"headline":"Appsmith: RCE via Supervisord XML-RPC Admin Interface Exposed via /supervisor Caddy Route","id":"CVE-2026-50189","kev_date_added":null,"published":"2026-06-24"},{"cvss_score":8.9,"headline":"Code injection in n/a","id":"CVE-2022-39824","kev_date_added":null,"published":"2022-09-05"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-25","vendors":["appsmithorg"]},"summary":"Authenticated users can bypass host restrictions to access internal loopback services via REST or GraphQL plugins.","url":"https://insights.sbomify.com/CVE-2026-55455/"}