{"answers":{"affected":"2 open source packages ship an affected version, including nocodb.","exploited":"There is no known exploitation of CVE-2026-46550 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46550 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46550 is a medium-severity vulnerability in nocodb, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-46550 and fix it if it is affected.\n\nWhat it is: CVE-2026-46550 is a medium-severity vulnerability in nocodb, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-46550 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nocodb (npm): affected all versions up to 0.301.3; no fix listed\n- nocodb (npm): affected all versions up to 0.301.3; 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-46550/ (Markdown: https://insights.sbomify.com/CVE-2026-46550/index.md)","id":"CVE-2026-46550","markdown":"https://insights.sbomify.com/CVE-2026-46550/index.md","name":"CVE-2026-46550","record":{"aliases":["GHSA-f74w-272x-mqcv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"NocoDB database tool","requires_auth":"none","summary":"Attackers can intercept refresh tokens over HTTP or exploit CSRF to hijack user sessions in NocoDB due to missing cookie security flags.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-614","name":"Sensitive Cookie in HTTPS Session Without 'Secure' Attribute"}],"description":"NocoDB is software for building databases as spreadsheets. Prior to 2026.04.1, the refresh-token cookie was set with httpOnly: true but missing both the secure flag and the sameSite attribute. Over plain HTTP the cookie could be intercepted on the network; without sameSite, browsers attached it to cross-site POSTs, enabling CSRF against the token-refresh endpoint. This vulnerability is fixed in 2026.04.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"NocoDB: Refresh Token Cookie Set Without `Secure` and `SameSite` Flags","id":"CVE-2026-46550","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"NocoDB: Missing File Size Enforcement in Upload-by-URL Allows Denial of Service via Disk Exhaustion","id":"CVE-2026-46551"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.301.3"],"package":"nocodb","purl":null,"source":"GHSA-f74w-272x-mqcv"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.301.3"],"package":"nocodb","purl":"pkg:npm/nocodb","source":"GHSA-f74w-272x-mqcv"}],"prev":{"headline":"NocoDB: OAuth Token Scope Not Enforced at ACL Layer Allows Scope Escalation","id":"CVE-2026-46549"},"products":["nocodb"],"published":"2026-06-23","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-24","vendors":["nocodb"]},"summary":"Attackers can intercept refresh tokens over HTTP or exploit CSRF to hijack user sessions in NocoDB due to missing cookie security flags.","url":"https://insights.sbomify.com/CVE-2026-46550/"}