{"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-73306 exists.","fix":"No fix has been published for CVE-2026-73306 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-73306 is a medium-severity vulnerability in budibase, published on 12 Aug 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-73306 and fix it if it is affected.\n\nWhat it is: CVE-2026-73306 is a medium-severity vulnerability in budibase, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73306 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-73306/ (Markdown: https://insights.sbomify.com/CVE-2026-73306/index.md)","id":"CVE-2026-73306","markdown":"https://insights.sbomify.com/CVE-2026-73306/index.md","name":"CVE-2026-73306","record":{"aliases":["GHSA-cr7p-cr3q-h5cm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Budibase low-code platform","requires_auth":"none","summary":"An unauthenticated attacker can enumerate valid email addresses and lock accounts by analyzing login failure response differences in Budibase.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-204","name":"Observable Response Discrepancy"}],"description":"Budibase is an open-source low-code platform. Prior to 3.39.25, POST /api/global/auth/:tenantId/login incremented the failure counter in packages/worker/src/api/controllers/global/auth.ts only for existing users, while packages/worker/src/middleware/emailLockout.ts returned X-Account-Locked and Retry-After only for locked identifiers. An unauthenticated attacker could compare the response after repeated failures to enumerate valid email addresses and temporarily lock valid accounts. This issue is fixed in version 3.39.25.","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: Account Enumeration via Login Lockout Response Differential","id":"CVE-2026-73306","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 bare fetch() in uploadUrl during AI table generation","id":"CVE-2026-73307"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["3.38.1"],"package":"@budibase/server","purl":null,"source":"GHSA-cr7p-cr3q-h5cm"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["3.38.1"],"package":"@budibase/server","purl":"pkg:npm/%40budibase/server","source":"GHSA-cr7p-cr3q-h5cm"}],"prev":{"headline":"Budibase: Privilege escalation via public role assignment API missing app-level authorization","id":"CVE-2026-73305"},"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-13","vendors":["Budibase"]},"summary":"An unauthenticated attacker can enumerate valid email addresses and lock accounts by analyzing login failure response differences in Budibase.","url":"https://insights.sbomify.com/CVE-2026-73306/"}