Live Active security incident? Get immediate response
CVE Record

CVE-2026-9497: changmingxie tcc-transaction Fastjson AutoType REST API Fastjson.parseObject deserialization

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.

MediumCVSS 6.5Not KEV-listed Updated
Discuss exposure Back to CVEs
Glexia's Take moderate

Analyst readout for executives and security teams

Plain-English summary

CVE-2026-9497 affects changmingxie tcc-transaction through unsafe Fastjson deserialization in a REST API component. A remote authenticated attacker may affect confidentiality, integrity, and availability. Public sources do not name a vendor fix, and the vendor reportedly did not respond to disclosure contact.

Executive priority

Prioritize review if tcc-transaction is used in production workflows, especially internet-facing or partner-facing systems. The issue is medium severity, but deserialization flaws can become serious when exposed through trusted API paths without strong access controls.

Technical view

The issue is reported in tcc-transaction up to 2.1.0, specifically Fastjson.parseObject in the Fastjson AutoType REST API. It is classified under CWE-20 and CWE-502. The CVSS v2 score is 6.5 with network access, low complexity, and required authentication.

Likely exposure

Exposure is most likely where tcc-transaction 2.0 or 2.1.0 is deployed and its REST API is reachable by authenticated users or services. Public internet exposure increases operational risk, but the source bundle does not confirm unauthenticated exploitation.

Exploitation context

The CVE record says remote attack is possible and the VulDB metadata references proof-of-concept maturity, but KEV is false and no cited source confirms active exploitation. Treat exploit availability as plausible but not proven operational exploitation.

Researcher notes

Evidence is limited to CVE and VulDB-style reporting. The vendor reportedly did not respond, and no official patch is named in the provided sources. Avoid assuming impact beyond partial confidentiality, integrity, and availability effects from the CVSS vector.

Mitigation direction

  • Inventory deployments of changmingxie tcc-transaction 2.0 and 2.1.0.
  • Check the project and vendor channels for official upgrade or mitigation guidance.
  • Restrict access to affected REST API endpoints to trusted authenticated users only.
  • Place exposed instances behind network controls or service-level allowlists.
  • Monitor logs for unusual authenticated API requests involving deserialization paths.

Validation and detection

  • Confirm whether tcc-transaction is present in application dependency manifests or runtime images.
  • Identify exposed REST API routes using tcc-transaction components.
  • Verify deployed versions against 2.0 and 2.1.0.
  • Review authentication boundaries for the affected API surface.
  • Check security monitoring for suspicious authenticated requests to those endpoints.
Prepared
Confidence
medium
Sources
6

Public sources used

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-9497 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profile CVE Program record
Severity
Medium
CVSS
6.5 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

4 CVSS vectors
6 Timeline events
1 ADP providers
5 Source links

SSVC decision data

CISA-ADP CISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

4 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

Score Version Severity Vector Exploit Impact Source
6.5 CVSS 2.0 Medium AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR 8 6.4 VulDB
6.3 CVSS 3.1 Medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 2.8 3.4 VulDB
6.3 CVSS 3.0 Medium CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 2.8 3.4 VulDB
5.3 CVSS 4.0 Medium 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 — — VulDB

Vulnerability scoring details

Base CVSS 4.0 score

5.3 Medium
CVSS 4.0 vector shape for CVE-2026-9497 Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timeline VulDB

    Advisory disclosed

  2. Source timeline VulDB

    VulDB entry created

  3. CVE reserved CVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timeline VulDB

    VulDB entry last update

  5. CVE published CVE Program

    The CVE record was published.

  6. CVE updated CVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADP CISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

Vendor Product Version / package Status
changmingxie tcc-transaction 2.0, 2.1.0 Listed
Weakness

CWE details

CWE-20CWE-502

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

CWE mapping pending import

This CVE carries a CWE mapping that will resolve to a full Glexia CWE intelligence page after the official CWE import is complete.

Open CWE intelligence Same-CWE CVEs
CWE-502 · source CWE mapping

CWE mapping pending import

This CVE carries a CWE mapping that will resolve to a full Glexia CWE intelligence page after the official CWE import is complete.

Open CWE intelligence Same-CWE CVEs