dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-9497

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw has been found in changmingxie tcc-transaction up to 2.1.0. This issue affects the function Fastjson.parseObject of the component Fastjson AutoType REST API. This manipulation causes deserialization. It is possible to initiate the attack remotely. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Deserialization vulnerability in Fastjson AutoType REST API within tcc-transaction library up to v2.1.0. Attackers can exploit Fastjson.parseObject via crafted JSON payloads to achieve remote code execution through unsafe deserialization.

MitigationUpgrade tcc-transaction beyond v2.1.0 or disable Fastjson AutoType feature; if upgrade unavailable, implement strict input validation and network segmentation to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if tcc-transaction is in use
    Search project dependencies, build files (pom.xml, build.gradle), or deployed artifacts for 'tcc-transaction' or 'changmingxie'
    Affected if The library is present in dependencies or deployed
  2. Check the installed version
    Locate the tcc-transaction JAR file or dependency declaration and identify the version number; compare to v2.1.0
    Affected if Version is 2.1.0 or lower (any version up to and including 2.1.0)
  3. Confirm Fastjson library is present
    Search for fastjson JAR files in the deployment or fastjson dependencies in build configuration
    Affected if Fastjson library is included in the project dependencies
  4. Verify AutoType is enabled in Fastjson configuration
    Inspect configuration files, application properties/yaml, or Java code for FastjsonParserConfig settings; look for 'autoTypeSupport' set to true or ParserConfig.getGlobalInstance().setAutoTypeSupport(true) calls
    Affected if AutoType support is explicitly enabled (set to true)
  5. Check if REST API endpoint is exposed
    Review application endpoints, controller mappings, or network exposure settings to determine if the Fastjson REST API component is accessible
    Affected if REST API endpoints using Fastjson.parseObject are externally accessible

User is affected if tcc-transaction version 2.1.0 or lower is in use AND Fastjson AutoType is enabled AND the REST API is exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade tcc-transaction beyond v2.1.0 or disable Fastjson AutoType feature; if upgrade unavailable, implement strict input validation and network segmentation to reduce attack surface.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9497 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9497 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data