{"answers":{"affected":"2 open source packages ship an affected version, including nocodb.","exploited":"There is no known exploitation of CVE-2026-47279 in the wild and no public exploit code.","fix":"Upgrade nocodb to 2026.05.1 or later.","what":"CVE-2026-47279 is a medium-severity vulnerability in nocodb, published on 23 Jun 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-47279 and fix it if it is affected.\n\nWhat it is: CVE-2026-47279 is a medium-severity vulnerability in nocodb, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47279 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nocodb (npm): affected all versions; fixed in 2026.05.1\n- nocodb (npm): affected all versions; fixed in 2026.05.1\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-47279/ (Markdown: https://insights.sbomify.com/CVE-2026-47279/index.md)","id":"CVE-2026-47279","markdown":"https://insights.sbomify.com/CVE-2026-47279/index.md","name":"CVE-2026-47279","record":{"aliases":["GHSA-9wgh-m22w-9xj8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"NocoDB database tool","requires_auth":"none","summary":"Attackers with a share UUID can read hidden LTAR column data in NocoDB public shared views due to missing visibility checks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the public shared-view relation endpoints accepted a caller-supplied column ID without verifying that the column was visible in the shared view, so anyone holding a share UUID could read links from any LTAR column on the view's table — including columns the view owner had hidden. publicMmList, publicHmList, and relDataList already ensured that the requested column belonged to the view's model, but did not check the view-column entry's show flag. 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":true,"headline":"NocoDB: Hidden LTAR Column Exposure in Public Shared-View Relation Endpoints","id":"CVE-2026-47279","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Azure Resource Manager Elevation of Privilege Vulnerability","id":"CVE-2026-47280"},"packages":[{"ecosystem":"npm","fixed":["2026.05.1"],"introduced":["0"],"last_affected":[],"package":"nocodb","purl":null,"source":"GHSA-9wgh-m22w-9xj8"},{"ecosystem":"npm","fixed":["2026.05.1"],"introduced":["0"],"last_affected":[],"package":"nocodb","purl":"pkg:npm/nocodb","source":"GHSA-9wgh-m22w-9xj8"}],"prev":{"headline":"Runtipi: Unauthenticated arbitrary file read through app-store logo symlinks","id":"CVE-2026-47277"},"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-24","vendors":["nocodb"]},"summary":"Attackers with a share UUID can read hidden LTAR column data in NocoDB public shared views due to missing visibility checks.","url":"https://insights.sbomify.com/CVE-2026-47279/"}