PYSEC-2026-2133

Vulnerability from pysec - Published: 2026-03-06 07:15 - Updated: 2026-07-13 05:48
VLAI
Details

CocoIndex is a data transformation framework for AI. Prior to version 0.3.34, the Doris target connector didn't verify the configured table name before creating some SQL statements (ALTER TABLE). So, in the application code, if the table name is provided by an untrusted upstream, it expose vulnerability to SQL injection when target schema change. This issue has been patched in version 0.3.34.

Impacted products
Name purl
cocoindex pkg:pypi/cocoindex

{
  "affected": [
    {
      "ecosystem_specific": {},
      "package": {
        "ecosystem": "PyPI",
        "name": "cocoindex",
        "purl": "pkg:pypi/cocoindex"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.3.34"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.1.43",
        "0.1.44",
        "0.1.45",
        "0.1.46",
        "0.1.47",
        "0.1.48",
        "0.1.49",
        "0.1.50",
        "0.1.51",
        "0.1.52",
        "0.1.53",
        "0.1.54",
        "0.1.55",
        "0.1.56",
        "0.1.57",
        "0.1.58",
        "0.1.59",
        "0.1.60",
        "0.1.61",
        "0.1.62",
        "0.1.63",
        "0.1.64",
        "0.1.65",
        "0.1.66",
        "0.1.67",
        "0.1.68",
        "0.1.69",
        "0.1.70",
        "0.1.71",
        "0.1.72",
        "0.1.73",
        "0.1.74",
        "0.1.75",
        "0.1.76",
        "0.1.77",
        "0.1.78",
        "0.1.79",
        "0.1.80",
        "0.1.81",
        "0.1.82",
        "0.1.83",
        "0.2.0",
        "0.2.1",
        "0.2.10",
        "0.2.11",
        "0.2.12",
        "0.2.13",
        "0.2.14",
        "0.2.15",
        "0.2.16",
        "0.2.17",
        "0.2.18",
        "0.2.19",
        "0.2.2",
        "0.2.20",
        "0.2.21",
        "0.2.22",
        "0.2.23",
        "0.2.3",
        "0.2.4",
        "0.2.5",
        "0.2.6",
        "0.2.7",
        "0.2.8",
        "0.2.9",
        "0.3.0",
        "0.3.1",
        "0.3.10",
        "0.3.11",
        "0.3.12",
        "0.3.13",
        "0.3.14",
        "0.3.15",
        "0.3.16",
        "0.3.17",
        "0.3.18",
        "0.3.19",
        "0.3.2",
        "0.3.20",
        "0.3.21",
        "0.3.22",
        "0.3.23",
        "0.3.24",
        "0.3.25",
        "0.3.26",
        "0.3.27",
        "0.3.28",
        "0.3.29",
        "0.3.3",
        "0.3.30",
        "0.3.31",
        "0.3.32",
        "0.3.33",
        "0.3.4",
        "0.3.5",
        "0.3.6",
        "0.3.7",
        "0.3.8",
        "0.3.9"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-28438",
    "GHSA-59g6-v3vg-f7wc"
  ],
  "details": "CocoIndex is a data transformation framework for AI. Prior to version 0.3.34, the Doris target connector didn\u0027t verify the configured table name before creating some SQL statements (ALTER TABLE). So, in the application code, if the table name is provided by an untrusted upstream, it expose vulnerability to SQL injection when target schema change. This issue has been patched in version 0.3.34.",
  "id": "PYSEC-2026-2133",
  "modified": "2026-07-13T05:48:18.867350Z",
  "published": "2026-03-06T07:15:58.770Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/cocoindex-io/cocoindex/security/advisories/GHSA-59g6-v3vg-f7wc"
    },
    {
      "type": "FIX",
      "url": "https://github.com/cocoindex-io/cocoindex/commit/ba2fc4a89e22d35572c64bd2990737c7913b0729"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…