Improper Input Validation in mindsdb

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS

• CVE-2023-49796: 0.49% estimated exploitation activity in the next 30 days; percentile 42.30 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The put method in mindsdb/mindsdb/api/http/namespaces/file.py does not validate the user-controlled name value, which is used in a temporary file name, which is afterwards opened for writing on lines 122-125, which leads to path injection. This issue may lead to arbitrary file write. This vulnerability allows for writing files anywhere on the server that the filesystem permissions that the running server has access to. Patches Use mindsdb staging branch or v23.11.4.1 References GHSL-2023-184 See CodeQL path injection prevention guidelines and OWASP guidelines.

Published by the source

12 Dec 2023, 00:49 UTC

Last modified by the source

22 Nov 2024, 18:40 UTC

Source last checked

26 Oct 2026, 13:27 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-crhp-7c74-cg4c

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-crhp-7c74-cg4c

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-49796

Advisory: Improper Input Validation in mindsdb
IDs: CVE-2023-49796, GHSA-crhp-7c74-cg4c
Record: https://patchnext.com/advisories/cve-2023-49796 (revision 2, source checked 26 Oct 2026, 13:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mindsdb 23.11.4.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mindsdb: affected < 23.11.4.1; fixed in 23.11.4.1

## Suggested inspection (read-only)
- `python -m pip show mindsdb`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mindsdb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-crhp-7c74-cg4c (OSV record GHSA-crhp-7c74-cg4c lists affected ranges: PyPI mindsdb >=0 <23.11.4.1 (fixed))
- Verified: https://github.com/advisories/GHSA-crhp-7c74-cg4c (GitHub-reviewed advisory GHSA-crhp-7c74-cg4c lists affected ranges: PyPI mindsdb >=0 <23.11.4.1)

Commands are suggestions: review each one before running it.