CVE-2025-70974: Fastjson before 1.2.48 mishandles autoType because, when an @type key is in a JSON document, and the value...
Fastjson before 1.2.48 mishandles autoType because, when an @type key is in a JSON document, and the value of that key is the name of a Java class, there may be calls to certain public methods of that class. Depending on the behavior of those methods, there may be JNDI injection with an attacker-supplied payload located elsewhere in that JSON document. This was exploited in the wild in 2023 through 2025. NOTE: this issue exists because of an incomplete fix for CVE-2017-18349. Also, a later bypass is covered by CVE-2022-25845.
Security readout for executives and security teams
Fastjson versions before 1.2.48 can mishandle JSON containing an @type value and may invoke Java class methods in unsafe ways. In some cases, this can lead to JNDI injection and full compromise. The CVE source says it was exploited in the wild from 2023 through 2025. Java applications are most likely exposed if they parse untrusted JSON with Alibaba Fastjson before 1.2.48, including shaded or bundled copies. Internet-facing APIs, message consumers, and services ingesting partner-supplied JSON deserve priority review. Treat this as urgent where legacy Fastjson handles untrusted input. The CVSS score is 10, impact can be complete compromise, and the source bundle states real-world exploitation. Prioritize internet-facing Java services first. Mitigation focus: Inventory applications and dependencies for Alibaba Fastjson before 1.2.48.; Upgrade affected Fastjson deployments to vendor-guided fixed or supported versions.; Review later Fastjson advisories, including the noted CVE-2022-25845 bypass..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-829: 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.
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.
2CVSS vectors
5Timeline events
2ADP providers
11Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
2 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-829 · source CWE mapping
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.