# TCC-TRANSACTION has an Improper Input Validation vulnerability

Advisory record · `GHSA-4r4v-3jc5-hrg9`

- **Identifiers:** `GHSA-4r4v-3jc5-hrg9` · `CVE-2026-9497`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 26 May 2026
- **Updated:** 30 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 26 May 2026, 13:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.mengyun:tcc-transaction` (Maven): affected `<=2.1.0`; no fixed version yet

## Machine-written summary

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

> The Maven package org.mengyun:tcc-transaction, versions up to and including 2.1.0, is affected by an improper input validation flaw. The flaw is in the Fastjson parseObject function used by its REST API, where crafted input can trigger unsafe deserialization. An attacker can exploit this remotely, but the source gives few details on the exact conditions or impact. No fixed version is listed, so no upgrade path is available from the source.

Written 2 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

- 5.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`, from CNA (VulDB)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 27th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4r4v-3jc5-hrg9)

## Sources

- [GitHub Advisory Database: GHSA-4r4v-3jc5-hrg9](https://github.com/advisories/GHSA-4r4v-3jc5-hrg9)
- [OSV: GHSA-4r4v-3jc5-hrg9](https://osv.dev/vulnerability/GHSA-4r4v-3jc5-hrg9)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-9497>
- <https://github.com/Ku4D3/bug_story/blob/main/report_01.md>
- <https://github.com/changmingxie/tcc-transaction>
- <https://vuldb.com/submit/814092>
- <https://vuldb.com/vuln/365480>
- <https://vuldb.com/vuln/365480/cti>

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-4r4v-3jc5-hrg9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4r4v-3jc5-hrg9/>. Everything for agents: <https://agentprime.io/llms.txt>.