CVE-2025-70974
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2025-70974 is a critical-severity Inclusion of Functionality from Untrusted Control Sphere (CWE-829) vulnerability in 360 (inferred from references). Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Supply Chain Compromise (T1195); ranked at the 50th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SR-4 (Provenance) and SR-11 (Component Authenticity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-70974 is a critical vulnerability in the Fastjson Java library versions prior to 1.2.48, stemming from improper handling of the autoType feature. Specifically, when a JSON document contains an @type key whose value specifies the name of a Java class, Fastjson may invoke certain public methods on that class. Depending on those methods' behavior, this can enable JNDI injection using an attacker-supplied payload embedded elsewhere in the same JSON document. The flaw represents an incomplete fix for CVE-2017-18349, with a related bypass addressed in CVE-2022-25845. It carries a CVSS v3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) and is associated with CWE-829 (Inclusion of Functionality from Untrusted Control Sphere).
The vulnerability can be exploited by unauthenticated remote attackers who supply malicious JSON input to applications parsing it with vulnerable Fastjson versions. By crafting a JSON payload with an @type field pointing to a controllable Java class and embedding a JNDI payload, attackers can trigger remote code execution (RCE) through JNDI lookups, potentially leading to full system compromise with high impacts on confidentiality, integrity, and availability across the affected scope.
Advisories and patch notes recommend upgrading to Fastjson 1.2.48 or later, as evidenced by the official changelog comparing versions 1.2.47 and 1.2.48 on GitHub. Additional resources, including exploitation proofs on Vulhub and Chinese advisories like CNVD-2019-22238, highlight disabling autoType or using whitelisting as interim measures where upgrading is not feasible.
This issue saw real-world exploitation from 2023 through 2025, including campaigns by actors like Androxgh0st, who compromised a US university to host C2 infrastructure, per CloudSEK analysis.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-1694
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 6 OS baselines
V14.2.3V3.5.6V9.1.3V15.3.2
Mitigating Controls (NIST 800-53 r5) AI
Requires documented, valid provenance for components, preventing acceptance of code from outside the trusted sphere.
Implements detection and prevention of counterfeit or inauthentic components before they are integrated.
Establishes processes to identify and address supply-chain weaknesses that would allow untrusted functionality.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Pre-acquisition integrity/authenticity checks directly prevent inclusion of untrusted code.
Supply-chain program directly governs inclusion of third-party executable code.
Contractual requirements can mandate trusted sources and integrity checks for included functionality.
Supplier risk assessment explicitly covers risks from their products and libraries.
Critical-supplier assessment reduces risk of importing executable functionality from untrusted parties.
Secure SDLC practices include dependency vetting and trusted-source policies.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
By requiring suppliers to propagate security requirements and to disclose component provenance, the control limits the inclusion of functionality obtained from untrusted third-party sources without oversight.
Blocking domains that serve malware or untrusted scripts prevents the browser from automatically including functionality from an attacker-controlled source.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248635 Executable search paths within the initialization files of all local interactive OL 8 users must only contain paths that resolve to the system default or the user's home directory. prevents CWE-829
Oracle Linux 9 (1 rule)
- V-271847 OL 9 must be configured so that executable search paths within the initialization files of all local interactive users must only contain paths that resolve to the system default or the users home directory. prevents CWE-829
RHEL 7 (1 rule)
- V-204477 The Red Hat Enterprise Linux operating system must be configured so that all local interactive user initialization files executable search paths contain only paths that resolve to the users home directory. prevents CWE-829
RHEL 8 (1 rule)
- V-230317 Executable search paths within the initialization files of all local interactive RHEL 8 users must only contain paths that resolve to the system default or the users home directory. prevents CWE-829
RHEL 9 (1 rule)
- V-258050 Executable search paths within the initialization files of all local interactive RHEL 9 users must only contain paths that resolve to the system default or the users home directory. prevents CWE-829
Windows 10 (1 rule)
- V-220737 Administrative accounts must not be used with applications that access the Internet, such as web browsers, or with potential Internet sources, such as email. prevents CWE-829