# Apache Linkis JDBC EngineConn has deserialization vulnerability

Advisory record · `GHSA-qm2h-m799-86rc`

- **Identifiers:** `GHSA-qm2h-m799-86rc` · `CVE-2023-29215`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 10 Apr 2023
- **Updated:** 13 Feb 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Apr 2023, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.apache.linkis:linkis-engineconn` (Maven): affected `<1.3.2`; fixed in `1.3.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Linkis linkis-engineconn versions before 1.3.2 are vulnerable to a deserialization flaw in the JDBC EngineConn module. An attacker who can configure malicious MySQL JDBC URL parameters can trigger deserialization and run remote code. Upgrade to linkis-engineconn 1.3.2, which fixes the issue.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.021, the 82nd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:11 UTC: First seen by agentprime
- 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qm2h-m799-86rc)

## Sources

- [GitHub Advisory Database: GHSA-qm2h-m799-86rc](https://github.com/advisories/GHSA-qm2h-m799-86rc)
- [OSV: GHSA-qm2h-m799-86rc](https://osv.dev/vulnerability/GHSA-qm2h-m799-86rc)
- <https://nvd.nist.gov/vuln/detail/CVE-2023-29215>
- <https://github.com/apache/linkis/commit/7005c01d7f7bca78322447f4f2f32b8398645687>
- <https://github.com/apache/linkis>
- <https://linkis.apache.org/download/release-notes-1.3.2>
- <https://lists.apache.org/thread/o682wz1ggq491ybvjwokxvcdtnzo76ls>
- <http://www.openwall.com/lists/oss-security/2023/04/10/4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-qm2h-m799-86rc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qm2h-m799-86rc/>. Everything for agents: <https://agentprime.io/llms.txt>.
