How severe is CVE-2023-35839?

CVE-2023-35839 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-35839?

CVE-2023-35839 affects the following packages: org.noear:solon (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-35839?

Update org.noear:solon to 2.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-35839 is resolved across your whole dependency graph.

How do I detect CVE-2023-35839 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.noear:solon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-35839 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2023-35839 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-35839, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-35839?

CVE-2023-35839 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-35839?

CVE-2023-35839 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2023-35839 published, and has it been updated?

CVE-2023-35839 was published on June 19, 2023 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2023-35839 — solon

CRITICAL

CVE-2023-35839 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.noear:solon. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.noear:solon — see the affected versions and patch details below.

Solon vulnerable to deserialization of untrusted data

Also known asGHSA-7q8c-49f4-4c8q

Published

Jun 19, 2023

Updated

Oct 21, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.noear:solon

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A bypass in the component sofa-hessian of Solon before v2.3.3 allows attackers to execute arbitrary code via providing crafted payload.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.noear:solon`	all versions	2.3.3`org.noear:solon:2.3.3`

Affected Products

1 product · 1 configurations

Application

solonsolon

< 2.3.3

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A bypass in the component sofa-hessian of Solon before v2.3.3 allows att…

github.comNVDJun 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.noear:solon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.noear:solon to 2.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-35839 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

A bypass in the component sofa-hessian of Solon before v2.3.3 allows attackers to execute arbitrary code via providing crafted payload.

O3 Security · Impact-Aware SCA

Is CVE-2023-35839 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-502Deserialization of Untrusted Data

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

solon

3.4/10

Maintained10/10

Code-Review0/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

Disclosed

Jun 19, 2023

First exploit

Jun 26, 2023

Last updated

Oct 21, 2026

Identifiers

CVE-2023-35839

GHSA-7q8c-49f4-4c8q

References

Advisorygithub.com · CVE 2023 35839.json Advisorynvd.nist.gov · CVE 2023 35839 Reportgithub.com Webgithub.com · v2.3.2...v2.3.3 Packagegithub.com · solon

Related vulnerabilities

Also affects solon

This CVE is critical severity, in line with the other 1 CVE affecting solon.

CVE-2023-48967

Same weakness: CWE-502

This CVE is critical severity; 1 of 7 other CVEs with CWE-502 is rated as high or higher (top: critical).

CVE-2026-115878CVE-2026-62848CVE-2026-115912CVE-2026-116580CVE-2026-114608CVE-2026-102554GHSA-673q-mjm6-r5xrBrowse all CWE-502

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 21, 2026

CVE-2023-35839 — solon

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2023-35839 in your dependencies?