How severe is CVE-2018-18240?

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

Which packages are affected by CVE-2018-18240?

CVE-2018-18240 affects the following packages: ro.pippo:pippo-core (Maven), ro.pippo:pippo-session (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-18240?

Update ro.pippo:pippo-core to 1.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-18240 is resolved across your whole dependency graph.

How do I detect CVE-2018-18240 in my Maven dependencies?

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

How do I mitigate CVE-2018-18240 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-2018-18240 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2018-18240, 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-2018-18240?

CVE-2018-18240 has an EPSS (Exploit Prediction Scoring System) score of 3.7%, placing it in the 90th 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-2018-18240?

CVE-2018-18240 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-2018-18240 published, and has it been updated?

CVE-2018-18240 was published on October 11, 2018 and was last updated on October 20, 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-2018-18240 — pippo-core

CRITICALFix: pippo-java/pippo@c6b2655

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

Pippo RCE Vulnerability

Also known asGHSA-h892-x453-86wc

Published

Oct 11, 2018

Updated

Oct 20, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

3.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% 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

2 pkgs affected

☕ro.pippo:pippo-core☕ro.pippo:pippo-session

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

Pippo through 1.11.0 allows remote code execution via a command to java.lang.ProcessBuilder because the XstreamEngine component does not use XStream's available protection mechanisms to restrict unmarshalling.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`ro.pippo:pippo-core`	all versions	1.12.0`ro.pippo:pippo-core:1.12.0`
☕Maven	`ro.pippo:pippo-session`	all versions	1.12.0`ro.pippo:pippo-session:1.12.0`

Affected Products

1 product · 1 configurations

Application

pippopippo

≤ 1.11.0

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.

Pippo through 1.11.0 allows remote code execution via a command to java.…

github.comNVDAug 2020

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ro.pippo:pippo-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ro.pippo:pippo-core to 1.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-18240 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

O3 Security · Impact-Aware SCA

Is CVE-2018-18240 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.0/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

pippo

3.7/10

Maintained0/10

Code-Review2/10

Branch-Protection0/10

Assessed Nov 2, 2026

Timeline

Disclosed

Oct 11, 2018

First exploit

Aug 24, 2020

Last updated

Oct 20, 2026

Identifiers

CVE-2018-18240

GHSA-h892-x453-86wc

References

Advisorynvd.nist.gov · CVE 2018 18240 Webgithub.com · c6b26551a82d2dd32097fcb17c13c3b830916296 Packagegithub.com · pippo Evidencegithub.com

Related vulnerabilities

Also affects pippo-core

This CVE is critical severity, in line with the other 2 CVEs affecting pippo-core.

CVE-2018-20059CVE-2018-18628

Same weakness: CWE-502

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

CVE-2026-114151CVE-2026-126187CVE-2026-115878CVE-2026-62848CVE-2026-115912CVE-2026-116580Browse all CWE-502

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2018-18240 — pippo-core

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-2018-18240 in your dependencies?