p PatchFirst

PatchFirst · Свежие уязвимости

nocodb 0.301.3: известные уязвимости · Страница 2

Известных уязвимостей, затрагивающих nocodb 0.301.3: 29. Сравните исправленные версии ниже с установленной у вас.

Фильтры уязвимостей
Сбросить фильтры

Уязвимостей: 29

  1. CVE-2026-47386

    Средний · CVSS 6.3EPSS 0,26%Есть исправление

    NocoDB: OAuth Authorization Code Race Condition

    NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, two concurrent token-exchange requests using the same OAuth authorization code could each mint a distinct valid (access_token, refresh_token) pair, breaking the single-use guarantee that PKCE relies on. This vulnerability is fixed in 2026.05.1.

    • Обновитесь до 2026.05.1
    Опубликовано Обновлено
  2. CVE-2026-47387

    Высокий · CVSS 8.4EPSS 0,4%Есть исправление

    NocoDB: Stored Cross-Site Scripting via Form View Redirect URL

    NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the shared form-view submit handler (packages/nc-gui/composables/useSharedFormViewStore.ts) in NocoDB writes the form's redirect_url to window.location.href after a same-host check that does not validate the URL scheme. A user with editor role (or above) on any base can plant a javascript: URL in the form's redirect_url; when an authenticated viewer opens the share-link and submits the form, the payload executes in the NocoDB origin and can read the session token from localStorage["nocodb-gui-v2"]. This vulnerability is fixed in 2026.05.1.

    • Обновитесь до 2026.05.1
    Опубликовано Обновлено
  3. CVE-2026-47388

    Низкий · CVSS 2.3EPSS 0,27%Есть исправление

    NocoDB: Missing Ownership Check in MCP Attachment Read

    NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, a low-privilege MCP token holder with knowledge of an attachment path could read any file in shared storage, including attachments belonging to other bases and workspaces, because the MCP readAttachment tool did not verify the file's ownership. This vulnerability is fixed in 2026.05.1.

    • Обновитесь до 2026.05.1
    Опубликовано Обновлено
  4. CVE-2026-53926

    Средний · CVSS 6.3EPSS 0,41%Есть исправление

    NocoDB: OAuth Tokens Persist Through Security Events

    NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, revokeAllOAuthTokensByUser in the users service is an empty stub being called from passwordChange, passwordForgot, and passwordReset. OAuth access and refresh tokens were not revoked when the user changed, reset, or recovered their password, leaving an attacker-issued OAuth grant valid after the user believed they had locked the attacker out. This vulnerability is fixed in 2026.05.1.

    • Обновитесь до 2026.05.1
    Опубликовано Обновлено
  5. CVE-2026-53927

    Средний · CVSS 5.1EPSS 0,39%Нет опубликованного исправления

    NocoDB: Server-Side Request Forgery via Spreadsheet Fetch URL

    NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the spreadsheet-fetch endpoint (axiosRequestMake) accepted URLs whose path contained a permitted extension anywhere in the string, and applied a hand-rolled regex blocklist that omitted 127.0.0.0/8 and 169.254.0.0/16, allowing the cloud-metadata endpoint to be reached with a crafted URL This vulnerability is fixed in 2026.05.1.

    Опубликовано Обновлено
  6. CVE-2026-53928

    Средний · CVSS 6.3EPSS 0,36%Нет опубликованного исправления

    NocoDB: Refresh Tokens Persist Through Password Recovery

    NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, a stolen refresh token survived a password-forgot flow and could be used to mint fresh JWTs even after the user reset their password. passwordChange and passwordReset deleted the user's refresh tokens, but passwordForgot only rotated token_version and revoked OAuth tokens — it did not call UserRefreshToken.deleteAllUserToken(user.id). An attacker holding a captured refresh cookie could still exchange it for a new access token after the victim triggered the recovery flow. This vulnerability is fixed in 2026.05.1.

    Опубликовано Обновлено
  7. CVE-2026-53929

    Средний · CVSS 5.1EPSS 0,4%Нет опубликованного исправления

    NocoDB: Stored Cross-Site Scripting via Secure Attachment

    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 vul

    Опубликовано Обновлено
  8. CVE-2026-53930

    Средний · CVSS 5.1EPSS 0,39%Нет опубликованного исправления

    NocoDB: Server-Side Request Forgery via Base Migration URL

    NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the base-migration endpoint accepted a caller-supplied URL that the migration worker dereferenced without enforcing protocol or destination, allowing scheme abuse (file:, ftp:, etc.) and probing of internal HTTP destinations. This vulnerability is fixed in 2026.05.1.

    Опубликовано Обновлено
  9. CVE-2026-53931

    Средний · CVSS 6.9EPSS 0,41%Нет опубликованного исправления

    NocoDB: Server-Side Request Forgery via Spreadsheet Import Endpoint

    NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the spreadsheet-import endpoint axiosRequestMake could be used as a generic HTTP proxy. Before the fix it was reachable unauthenticated, and its URL-extension allowlist was a regex tested against the full URL string, so URLs whose query string ended in .csv satisfies the gate even though the underlying request is for another file. This vulnerability is fixed in 2026.05.1.

    Опубликовано Обновлено

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →