How severe is CVE-2018-20059?

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

Which packages are affected by CVE-2018-20059?

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

How do I fix CVE-2018-20059?

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-20059 is resolved across your whole dependency graph.

How do I detect CVE-2018-20059 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-20059 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2018-20059 actively exploited in the wild?

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

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

CVE-2018-20059 is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2018-20059 published, and has it been updated?

CVE-2018-20059 was published on December 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-20059 — pippo-core

CRITICALFix: pippo-java/pippo@9f36e58

CVE-2018-20059 is a critical-severity (CVSS 9.8) XML External Entity (XXE) 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.

Improper Restriction of XML External Entity Reference in pippo-core

Also known asGHSA-rmm5-g63h-m6g9

Published

Dec 11, 2018

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

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

☕ro.pippo:pippo-core

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

jaxb/JaxbEngine.java in Pippo 1.11.0 allows XXE.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

pippopippo

1 version

1.11.0

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.

jaxb/JaxbEngine.java in Pippo 1.11.0 allows XXE.

github.comNVDJan 2019

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-20059 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

jaxb/JaxbEngine.java in Pippo 1.11.0 allows XXE.

O3 Security · Impact-Aware SCA

Is CVE-2018-20059 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-611XML External Entity (XXE)

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

Code-Review2/10

Maintained0/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

Disclosed

Dec 11, 2018

First exploit

Jan 3, 2019

Last updated

Oct 20, 2026

Identifiers

CVE-2018-20059

GHSA-rmm5-g63h-m6g9

References

Advisorynvd.nist.gov · CVE 2018 20059 Advisorygithub.com · GHSA rmm5 g63h m6g9 Reportgithub.com Webgithub.com · 9f36e5891c0b11f840e1e1561ae96d83ba9ce759 Packagegithub.com · pippo

Related vulnerabilities

Also affects pippo-core

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

CVE-2018-18240CVE-2018-18628

Same weakness: CWE-611

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

CVE-2026-126062CVE-2026-108358CVE-2026-108357CVE-2026-61586CVE-2026-61741CVE-2026-61570Browse all CWE-611

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2018-20059 — 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-20059 in your dependencies?