NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

Pippo RCE VulnerabilityGHSA-h892-x453-86wc

CRITICALFix: pippo-java/pippo@c6b2655

GHSA-h892-x453-86wc 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.

Also known asCVE-2018-18240
Published
Updated
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
2.07%2.77%3.46%4.15%2.6%3.7%May 26Sep 26Nov 26

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
EcosystemPackageVulnerable rangeFix
☕Mavenro.pippo:pippo-coreall versions1.12.0ro.pippo:pippo-core:1.12.0
☕Mavenro.pippo:pippo-sessionall versions1.12.0ro.pippo:pippo-session:1.12.0

Affected Products

1 product · 1 configurations
Application
pippopippo
≤ 1.11.0
range
Exploits & PoCs
1

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

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. 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 GHSA-h892-x453-86wc is resolved across your whole dependency graph.

  3. 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

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.
O3 Security · Impact-Aware SCA

Is GHSA-h892-x453-86wc in your dependencies?

Find it across Maven, including transitive dependencies.

Pippo RCE Vulnerability (Critical 9.8)