Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-70974 critical CVSS 10.0

Vulnerability in com.alibaba:fastjson (CVE-2025-70974)

Summary

Vulnerability in com.alibaba:fastjson (CVE-2025-70974). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.2.48 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-70974 has been found in com.alibaba:fastjson.
Successful exploitation can lead to full system takeover. CVSS score: 10.0/10.
What to do: upgrade com.alibaba:fastjson to 1.2.48 or later.
If unsure, ask your IT team or search "com.alibaba:fastjson CVE-2025-70974" on the vendor's site.

CVE-2025-70974 (com.alibaba:fastjson) — CWE-829 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.2.48 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-829) exists in com.alibaba:fastjson.

📍 Affected scope

Check the vendor advisory for the affected versions of com.alibaba:fastjson.

🔥 Severity

Severity: Critical (CVSS 10.0/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.2.48.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで com.alibaba:fastjson を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade com.alibaba:fastjson to 1.2.48

    ステージング環境で 1.2.48 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven com.alibaba:fastjson
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.48"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details