{"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-73409 exists.","fix":"No fix has been published for CVE-2026-73409 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-73409 is a medium-severity vulnerability in budibase, published on 12 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-73409 and fix it if it is affected.\n\nWhat it is: CVE-2026-73409 is a medium-severity vulnerability in budibase, published on 12 Aug 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-73409 exists.\n\nAffected packages and fixed versions:\n- @budibase/server (npm): affected all versions up to 3.38.1; no fix listed\n- @budibase/server (npm): affected all versions up to 3.38.1; no fix listed\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-73409/ (Markdown: https://insights.sbomify.com/CVE-2026-73409/index.md)","id":"CVE-2026-73409","markdown":"https://insights.sbomify.com/CVE-2026-73409/index.md","name":"CVE-2026-73409","record":{"aliases":["GHSA-ppr4-5f46-j9c6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Budibase low-code platform","requires_auth":"high_privilege","summary":"A builder can determine the existence and readability of server files by manipulating MongoDB TLS certificate paths, exposing sensitive filesystem information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"Budibase is an open-source low-code platform. Prior to 3.40.1, packages/server/src/integrations/mongodb.ts passed builder-controlled tlsCertificateKeyFile and tlsCAFile values directly to MongoClient on Budibase Cloud. A builder could submit absolute server paths through /api/datasources/verify and distinguish readable existing files from missing files by comparing the driver error, exposing a filesystem existence and readability oracle on the shared server. This issue is fixed in version 3.40.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Budibase: Server Filesystem Existence/Read Oracle via Builder-Controlled MongoDB tlsCertificateKeyFile","id":"CVE-2026-73409","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Budibase: SSRF via DNS rebinding in the REST datasource integration","id":"CVE-2026-73410"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["3.38.1"],"package":"@budibase/server","purl":null,"source":"GHSA-ppr4-5f46-j9c6"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["3.38.1"],"package":"@budibase/server","purl":"pkg:npm/%40budibase/server","source":"GHSA-ppr4-5f46-j9c6"}],"prev":{"headline":"Budibase: MySQL DESCRIBE Backtick Injection via multipleStatements in Database Connector","id":"CVE-2026-73408"},"products":["budibase"],"published":"2026-08-12","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["Budibase"]},"summary":"A builder can determine the existence and readability of server files by manipulating MongoDB TLS certificate paths, exposing sensitive filesystem information.","url":"https://insights.sbomify.com/CVE-2026-73409/"}