Vulnerability in nocodb (CVE-2026-47279)
Summary
Vulnerability in nocodb (CVE-2026-47279). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v2/public/shared-view/. Mitigation: upgrade to 2026.05.1 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47279 has been found in nocodb.
Attackers can target a specific entry point like GET /api/v2/public/shared-view/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade nocodb to 2026.05.1 or later.
If unsure, ask your IT team or search "nocodb CVE-2026-47279" on the vendor's site.
CVE-2026-47279 (nocodb) — CWE-284
Attack surface: GET /api/v2/public/shared-view/ / publicMmList / publicHmList / relDataList
Patched: 2026.05.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in nocodb. Attackers reach the vulnerable code path via GET /api/v2/public/shared-view/.
Check the vendor advisory for the affected versions of nocodb. Attack surface: GET /api/v2/public/shared-view/ / publicMmList / publicHmList / relDataList.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2026.05.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v2/public/shared-view/ requests with malformed payloads or SQL meta-characters. Run grep -r 'nocodb' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'nocodb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nocodbを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v2/public/shared-view/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v2/public/shared-view/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade nocodb to 2026.05.1ステージング環境で 2026.05.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v2/public/shared-view/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com