Authenticated class instantiation via unsafe AutoType parsing
Published May 25, 2026 · Updated May 25, 2026
Unsafe deserialization in changmingxie tcc-transaction 2.0 through 2.1.0 allows remote authenticated users to instantiate classes. The recovery path reads stored transaction JSON from Redis and passes attacker-controlled @type metadata to Fastjson.parseObject with AutoType enabled. Access to write transaction state through the REST API or Redis is required, after which recovery processing creates the selected class inside the service.
Summary
What happened
Unsafe deserialization in changmingxie tcc-transaction 2.0 through 2.1.0 allows remote authenticated users to instantiate classes. The recovery path reads stored transaction JSON from Redis and passes attacker-controlled @type metadata to Fastjson.parseObject with AutoType enabled. Access to write transaction state through the REST API or Redis is required, after which recovery processing creates the selected class inside the service.
The record
- CVE
- CVE-2026-9497
- Published
- May 25, 2026
- Updated
- May 25, 2026
- Vendor
- changmingxie
- Product
- tcc-transaction
- Classifications
- CWE-20, CWE-502, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 25, 2026CVE publishedPublication date reported by the CVE source.
- May 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0
- Affected versionversion=2.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo