{"answers":{"affected":"2 open source packages ship an affected version, including @budibase/server.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48153 exists.","fix":"Upgrade @budibase/server to 3.39.0 or later.","what":"CVE-2026-48153 is a high-severity server-side request forgery vulnerability in budibase, published on 27 May 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-48153 and fix it if it is affected.\n\nWhat it is: CVE-2026-48153 is a high-severity server-side request forgery vulnerability in budibase, published on 27 May 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-48153 exists.\n\nAffected packages and fixed versions:\n- @budibase/server (npm): affected all versions; fixed in 3.39.0\n- @budibase/server (npm): affected all versions; fixed in 3.39.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-48153/ (Markdown: https://insights.sbomify.com/CVE-2026-48153/index.md)","id":"CVE-2026-48153","markdown":"https://insights.sbomify.com/CVE-2026-48153/index.md","name":"CVE-2026-48153","record":{"aliases":["GHSA-4q6h-8p4v-67vq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Budibase low-code platform","requires_auth":"low_privilege","summary":"Attackers can exploit missing URL validation in Budibase's OAuth2 token endpoint to access internal network resources and cloud metadata.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Budibase is an open-source low-code platform. Prior to 3.39.0, fetchToken in the OAuth2 SDK makes a POST to a builder-supplied URL with plain node-fetch, skipping the blacklist.isBlacklisted check that every other outbound fetch path in the codebase uses. The Joi schema for the OAuth2 URL has no scheme or host restriction. This vulnerability is fixed in 3.39.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Budibase: SSRF via OAuth2 token endpoint URL reaches internal hosts and cloud metadata","id":"CVE-2026-48153","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"GoRest: InMemorySecret2FA race condition allows process crash via concurrent map access","id":"CVE-2026-48154"},"packages":[{"ecosystem":"npm","fixed":["3.39.0"],"introduced":["0"],"last_affected":[],"package":"@budibase/server","purl":null,"source":"GHSA-4q6h-8p4v-67vq"},{"ecosystem":"npm","fixed":["3.39.0"],"introduced":["0"],"last_affected":[],"package":"@budibase/server","purl":"pkg:npm/%40budibase/server","source":"GHSA-4q6h-8p4v-67vq"}],"prev":{"headline":"Budibase: Basic app users can exfiltrate stored REST datasource auth by rewriting datasource base URL","id":"CVE-2026-48152"},"products":["budibase"],"published":"2026-05-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-05-27","vendors":["Budibase"]},"summary":"Attackers can exploit missing URL validation in Budibase's OAuth2 token endpoint to access internal network resources and cloud metadata.","url":"https://insights.sbomify.com/CVE-2026-48153/"}