LiveActive security incident?Get immediate response
CVE Record

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.

CriticalCVSS 10Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-70974 is a critical Fastjson autoType flaw. If an application parses attacker-controlled JSON with older Fastjson behavior, a crafted @type value may trigger dangerous Java class methods and enable JNDI-based compromise. The record says exploitation occurred in the wild from 2023 through 2025.

Executive priority

Treat as an urgent dependency-risk review for Java-facing services. The CVSS 10 score and reported in-the-wild exploitation justify accelerated inventory and remediation, especially for internet-exposed APIs. Do not assume the environment is safe until transitive dependencies are checked.

Technical view

Fastjson before 1.2.48 mishandles autoType processing when @type names a Java class. Certain public methods may be called during parsing, creating JNDI injection risk from attacker-controlled JSON content. The CVE states this is an incomplete fix for CVE-2017-18349, with a later bypass tracked as CVE-2022-25845.

Likely exposure

Highest concern is Java services, APIs, or middleware that accept untrusted JSON and include Alibaba Fastjson versions before 1.2.48. Exposure metadata in the supplied record is inconsistent, so teams should verify actual dependency versions and vendor advisories rather than relying only on product status fields.

Exploitation context

The CVE description explicitly states exploitation in the wild during 2023 through 2025. It is not listed as KEV in the supplied bundle. Public references include research and reproduction material, so assume attacker familiarity is mature without using those materials operationally.

Researcher notes

The supplied CVE asserts the vulnerable range as before 1.2.48, but the affected-product metadata appears incomplete or contradictory. Validate against upstream Fastjson changes and vendor advisories. Avoid treating 1.2.48 as a universal endpoint because the record notes a later bypass in CVE-2022-25845.

Mitigation direction

  • Inventory all Java applications and transitive dependencies for Fastjson usage.
  • Prioritize replacement or upgrade of Fastjson versions before 1.2.48.
  • Review Alibaba/Fastjson and Red Hat guidance for supported remediation status.
  • Account for related issues CVE-2017-18349 and CVE-2022-25845 during remediation.
  • Restrict exposure of JSON parsing endpoints accepting untrusted input where feasible.

Validation and detection

  • Check SBOMs, build files, and runtime classpaths for Fastjson versions.
  • Confirm whether internet-facing services parse untrusted JSON with Fastjson.
  • Review logs for suspicious requests containing @type fields.
  • Verify remediation against vendor guidance, not only package version strings.
  • Confirm downstream products are not bundling vulnerable Fastjson copies.
Prepared
Confidence
medium
Sources
9

Public sources used

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-70974 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 profileCVE Program record
Severity
Critical
CVSS
10 (3.1)
Known Exploited
No
Published

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

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.

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.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96mitre
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2025-70974Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

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

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

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

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPfastjson: Fastjson: Remote Code Execution via JNDI Injection due to autoType mishandling
other:Red Hat severity ratingcvssV3_1
  • 2026-01-09T07:02:15.514Z: Reported to Red Hat.
  • 2026-01-09T06:43:23.584Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AlibabaFastjson0unaffected
Weakness

CWE details

CWE-829

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