{"answers":{"affected":"2 open source packages ship an affected version, including nocodb.","exploited":"There is no known exploitation of CVE-2026-53929 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53929 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53929 is a medium-severity cross-site scripting vulnerability in nocodb, published on 23 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-53929 and fix it if it is affected.\n\nWhat it is: CVE-2026-53929 is a medium-severity cross-site scripting vulnerability in nocodb, published on 23 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-53929 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-53929/ (Markdown: https://insights.sbomify.com/CVE-2026-53929/index.md)","id":"CVE-2026-53929","markdown":"https://insights.sbomify.com/CVE-2026-53929/index.md","name":"CVE-2026-53929","record":{"aliases":["GHSA-6mhr-74x2-98v9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"NocoDB database spreadsheet","requires_auth":"low_privilege","summary":"Authenticated users can execute arbitrary scripts via malicious HTML or SVG attachments when secure attachments are enabled, due to header key mismatches.","user_interaction":"required","vuln_class":"xss"},"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:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, with NC_SECURE_ATTACHMENTS=true, an authenticated uploader could deliver .html or .svg attachments that the browser rendered inline from the NocoDB origin instead of forcing a download. The signed attachment handler stored response-header overrides under PascalCase keys (ResponseContentDisposition, ResponseContentType) while the controller that served the file read them under lowercase-hyphen names (response-content-disposition). The mismatch dropped the Content-Disposition: attachment header, leaving Express to auto-render .html, .svg, and similar inline. This vulnerability is fixed in 2026.05.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: Stored Cross-Site Scripting via Secure Attachment","id":"CVE-2026-53929","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"NocoDB: Server-Side Request Forgery via Base Migration URL","id":"CVE-2026-53930"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.301.3"],"package":"nocodb","purl":null,"source":"GHSA-6mhr-74x2-98v9"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.301.3"],"package":"nocodb","purl":"pkg:npm/nocodb","source":"GHSA-6mhr-74x2-98v9"}],"prev":{"headline":"NocoDB: Refresh Tokens Persist Through Password Recovery","id":"CVE-2026-53928"},"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-25","vendors":["nocodb"]},"summary":"Authenticated users can execute arbitrary scripts via malicious HTML or SVG attachments when secure attachments are enabled, due to header key mismatches.","url":"https://insights.sbomify.com/CVE-2026-53929/"}