{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-50147 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-50147 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-50147 is a high-severity path traversal vulnerability in metabase, published on 15 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-50147 and fix it if it is affected.\n\nWhat it is: CVE-2026-50147 is a high-severity path traversal vulnerability in metabase, published on 15 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-50147 in the wild and no public exploit code.\n\nAffected product: metabase. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-50147/ (Markdown: https://insights.sbomify.com/CVE-2026-50147/index.md)","id":"CVE-2026-50147","markdown":"https://insights.sbomify.com/CVE-2026-50147/index.md","name":"CVE-2026-50147","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Metabase BI tool","requires_auth":"high_privilege","summary":"An attacker with database connection configuration privileges can read arbitrary files from the Metabase server filesystem via unsafe JDBC parameters.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"metabase","vendor":"metabase"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"Metabase is an open-source business intelligence and embedded analytics tool. From 1.57.0 until 1.57.19.1, 1.58.14.1, 1.59.10, and 1.60.4, an attacker who can configure a Metabase database connection can read arbitrary files from the Metabase server's filesystem by adding unsafe JDBC parameters to a MySQL or MariaDB connection, causing the driver to read files from the Metabase host and expose the contents through queries against the connected database or through validation error messages. This issue is fixed in versions 1.57.19.1, 1.58.14.1, 1.59.10, and 1.60.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Metabase: Arbitrary File Read via MySQL Connection Property Injection","id":"CVE-2026-50147","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Metabase: Remote Code Execution via Snowflake JDBC Driver Arbitrary File Write","id":"CVE-2026-50148"},"packages":[],"prev":{"headline":"Astro: Reflected XSS via unescaped slot name","id":"CVE-2026-50146"},"products":["metabase"],"published":"2026-07-15","related":[{"cvss_score":10,"headline":"Metabase SQL Injection","id":"CVE-2026-72898","kev_date_added":"2026-08-11","published":"2026-08-10"},{"cvss_score":10,"headline":"Metabase GeoJSON API Local File Inclusion","id":"CVE-2021-41277","kev_date_added":"2024-11-12","published":"2021-11-17"},{"cvss_score":10,"headline":"Metabase: Remote Code Execution via Snowflake JDBC Driver Arbitrary File Write","id":"CVE-2026-50148","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":10,"headline":"Metabase vulnerable to remote code execution via POST /api/setup/validate API endpoint","id":"CVE-2023-37470","kev_date_added":null,"published":"2023-08-04"},{"cvss_score":9.9,"headline":"Metabase: Unsafe Deserialization of H2 Query Results","id":"CVE-2026-59827","kev_date_added":null,"published":"2026-07-09"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2023-38646","kev_date_added":null,"published":"2023-07-21"},{"cvss_score":9.1,"headline":"Metabase: Arbitrary Code Execution via Database Connection Detail Bypass","id":"CVE-2026-59826","kev_date_added":null,"published":"2026-07-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-07-15","vendors":["metabase"]},"summary":"An attacker with database connection configuration privileges can read arbitrary files from the Metabase server filesystem via unsafe JDBC parameters.","url":"https://insights.sbomify.com/CVE-2026-50147/"}