{"answers":{"affected":"2 open source packages ship an affected version, including nocodb.","exploited":"There is no known exploitation of CVE-2026-46548 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46548 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46548 is a medium-severity server-side request forgery vulnerability in nocodb, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46548 and fix it if it is affected.\n\nWhat it is: CVE-2026-46548 is a medium-severity server-side request forgery vulnerability in nocodb, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-46548 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-46548/ (Markdown: https://insights.sbomify.com/CVE-2026-46548/index.md)","id":"CVE-2026-46548","markdown":"https://insights.sbomify.com/CVE-2026-46548/index.md","name":"CVE-2026-46548","record":{"aliases":["GHSA-2c5x-4jgf-88mj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"NocoDB database platform","requires_auth":"low_privilege","summary":"Authenticated users can bypass SSRF protections in notification plugins to send requests to internal hosts, potentially exposing internal data.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"NocoDB is software for building databases as spreadsheets. Prior to 2026.04.1, the request-filtering-agent SSRF protection was non-functional in the four notification webhook plugins (Slack, Discord, Mattermost, Teams) because httpAgent / httpsAgent were passed as part of the request body rather than the axios config. An authenticated user with hook-creation permission could direct outbound POST requests to arbitrary internal hosts. 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: SSRF Protection Bypass in Notification Webhook Plugins (Slack, Discord, Mattermost, Teams)","id":"CVE-2026-46548","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"NocoDB: OAuth Token Scope Not Enforced at ACL Layer Allows Scope Escalation","id":"CVE-2026-46549"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.301.3"],"package":"nocodb","purl":null,"source":"GHSA-2c5x-4jgf-88mj"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.301.3"],"package":"nocodb","purl":"pkg:npm/nocodb","source":"GHSA-2c5x-4jgf-88mj"}],"prev":{"headline":"NocoDB: Reflected Cross-Site Scripting via Page Leaving Redirect URL","id":"CVE-2026-46547"},"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":"Authenticated users can bypass SSRF protections in notification plugins to send requests to internal hosts, potentially exposing internal data.","url":"https://insights.sbomify.com/CVE-2026-46548/"}