CVE-2022-25845

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 17.8%, top 3% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 18%CVSS: 8.1Exploit: NoneExposed: 0

A fix is available — apply it.

The package com.alibaba:fastjson before 1.2.83 are vulnerable to Deserialization of Untrusted Data by bypassing the default autoType shutdown restrictions, which is possible under certain conditions. Exploiting this vulnerability allows attacking remote servers. Workaround: If upgrading is not possible, you can enable safeMode.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
—
EPSS
96.8%
KEV
Not listed

Published

June 10, 2022

Last Modified

November 21, 2024

References (14)

Vendor Advisories for CVE-2022-25845(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatfastjson2022-07-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
com.alibaba:fastjson1.2.25 ... 1.2.80 (104 versions)1.2.83—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 22:56 UTCEG score recompute▼ 0.90
  2. 2026-07-22 14:06 UTCEPSS rescore
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-20 17:05 UTCEPSS rescore
  7. 2026-07-19 02:27 UTCEPSS rescore
  8. 2026-07-18 10:02 UTCEPSS rescore
  9. 2026-07-18 10:02 UTCEPSS rescore
  10. 2026-07-17 08:16 UTCOSV refresh
  11. 2026-07-16 17:00 UTCEPSS rescore
  12. 2026-07-16 17:00 UTCEPSS rescore
  13. 2026-07-15 16:56 UTCEPSS rescore
  14. 2026-07-15 16:56 UTCEPSS rescore
  15. 2026-07-15 01:58 UTCEPSS rescore
  16. 2026-07-15 01:58 UTCEPSS rescore
  17. 2026-07-13 22:27 UTCEPSS rescore
  18. 2026-07-13 06:11 UTCEPSS rescore
  19. 2026-07-13 06:11 UTCEPSS rescore
  20. 2026-07-12 05:44 UTCEPSS rescore
  21. 2026-07-11 08:25 UTCEPSS rescore
  22. 2026-07-09 19:07 UTCEPSS rescore
  23. 2026-07-08 15:12 UTCEPSS rescore
  24. 2026-07-07 13:44 UTCEPSS rescore
  25. 2026-07-06 16:25 UTCEPSS rescore
Show 59 more
  1. 2026-07-06 16:25 UTCEPSS rescore
  2. 2026-07-05 02:28 UTCEPSS rescore
  3. 2026-07-04 06:29 UTCEPSS rescore
  4. 2026-07-04 06:29 UTCEPSS rescore
  5. 2026-07-01 15:04 UTCEPSS rescore
  6. 2026-06-30 23:20 UTCEPSS rescore
  7. 2026-06-30 23:20 UTCEPSS rescore
  8. 2026-06-29 06:32 UTCOSV refresh
  9. 2026-06-28 14:06 UTCEPSS rescore
  10. 2026-06-28 04:54 UTCEPSS rescore
  11. 2026-06-28 04:54 UTCEPSS rescore
  12. 2026-06-27 03:07 UTCEPSS rescore
  13. 2026-06-25 13:48 UTCEPSS rescore
  14. 2026-06-24 14:03 UTCEPSS rescore
  15. 2026-06-24 14:03 UTCEPSS rescore
  16. 2026-06-23 21:31 UTCEPSS rescore
  17. 2026-06-23 21:31 UTCEPSS rescore
  18. 2026-06-22 14:24 UTCEPSS rescore
  19. 2026-06-21 14:55 UTCEPSS rescore
  20. 2026-06-21 14:55 UTCEPSS rescore
  21. 2026-06-21 01:58 UTCEPSS rescore
  22. 2026-06-21 01:58 UTCEPSS rescore
  23. 2026-06-19 19:24 UTCEPSS rescore
  24. 2026-06-19 19:24 UTCEPSS rescore
  25. 2026-06-18 17:51 UTCEPSS rescore
  26. 2026-06-18 17:51 UTCEPSS rescore
  27. 2026-06-17 17:51 UTCEPSS rescore
  28. 2026-06-17 17:51 UTCEPSS rescore
  29. 2026-06-16 17:51 UTCEPSS rescore
  30. 2026-06-15 17:46 UTCEPSS rescore
  31. 2026-06-13 22:58 UTCEPSS rescore
  32. 2026-06-13 22:58 UTCEPSS rescore
  33. 2026-06-12 23:10 UTCEPSS rescore
  34. 2026-06-12 23:10 UTCEPSS rescore
  35. 2026-06-11 23:57 UTCOSV refresh
  36. 2026-06-10 22:16 UTCEPSS rescore
  37. 2026-06-10 13:20 UTCEPSS rescore
  38. 2026-06-07 15:23 UTCEPSS rescore
  39. 2026-06-07 15:23 UTCEPSS rescore
  40. 2026-06-06 13:46 UTCEPSS rescore
  41. 2026-06-06 13:46 UTCEPSS rescore
  42. 2026-06-05 22:45 UTCEPSS rescore
  43. 2026-06-05 06:09 UTCEPSS rescore
  44. 2026-06-05 06:09 UTCEPSS rescore
  45. 2026-06-04 13:11 UTCEPSS rescore
  46. 2026-06-04 13:11 UTCEPSS rescore
  47. 2026-06-01 13:50 UTCEPSS rescore
  48. 2026-06-01 13:50 UTCEPSS rescore
  49. 2026-06-01 13:50 UTCEPSS rescore
  50. 2026-05-31 22:29 UTCEPSS rescore
  51. 2026-05-31 22:29 UTCEPSS rescore
  52. 2026-05-29 13:42 UTCEPSS rescore
  53. 2026-05-28 13:43 UTCEPSS rescore
  54. 2026-05-28 13:43 UTCEPSS rescore
  55. 2026-05-28 13:43 UTCEPSS rescore
  56. 2026-05-26 07:17 UTCEPSS rescore
  57. 2026-05-26 07:17 UTCEPSS rescore
  58. 2026-05-25 20:49 UTCEG score recompute
  59. 2026-05-25 20:49 UTCVendor advisory

Publicly available exploits

(3 references)

Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCph0ebus/CVE-2022-25845-In-Spring
    First seen Nov 26, 2024

    exploit by python

    Open source ↗
  • GitHub PoCluelueking/CVE-2022-25845-In-Spring
    First seen Nov 7, 2024

    CVE-2022-25845(fastjson1.2.80) exploit in Spring Env!

    Open source ↗
  • GitHub PoChosch3n/FastjsonVulns
    First seen Sep 1, 2022

    [fastjson 1.2.80] CVE-2022-25845 aspectj fileread & groovy remote classload

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-25845?
CVE-2022-25845 is a high vulnerability published on June 10, 2022. The package com.alibaba:fastjson before 1.2.83 are vulnerable to Deserialization of Untrusted Data by bypassing the default autoType shutdown restrictions, which is possible under certain conditions. Exploiting this vulnerability allows attacking remote servers. Workaround: If upgrading is not…
When was CVE-2022-25845 disclosed?
CVE-2022-25845 was first published in the National Vulnerability Database on June 10, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-25845 actively exploited?
CVE-2022-25845 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-25845?
CVE-2022-25845 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2022-25845?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-25845, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-25845

Explore →

Is Your Infrastructure Affected by CVE-2022-25845?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs