How severe is CVE-2018-10899?

CVE-2018-10899 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-10899?

CVE-2018-10899 affects the following packages: org.jolokia:jolokia-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-10899?

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

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

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

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

No public exploit code has been indexed for CVE-2018-10899 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2018-10899?

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

CVE-2018-10899 is classified as Improper Input Validation (CWE-20), Cross-Site Request Forgery (CSRF) (CWE-352). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2018-10899 was published on August 1, 2019 and was last updated on October 24, 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

HIGH severity

CVE-2018-10899 — jolokia-core

HIGH

CVE-2018-10899 is a high-severity (CVSS 8.8) Improper Input Validation vulnerability in org.jolokia:jolokia-core. A fix is available for org.jolokia:jolokia-core — see the affected versions and patch details below.

Cross-Site Request Forgery in Jolokia

Also known asGHSA-xcxf-7q4p-cj26

Published

Aug 1, 2019

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% 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.jolokia:jolokia-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

A flaw was found in Jolokia versions from 1.2 to before 1.6.1. Affected versions are vulnerable to a system-wide CSRF. This holds true for properly configured instances with strict checking for origin and referrer headers. This could result in a Remote Code Execution attack.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jolokia:jolokia-core`	≥ 1.2&&< 1.6.1	1.6.1`org.jolokia:jolokia-core:1.6.1`

Affected Products

2 products · 2 configurations

Application

jolokiajolokia

≥ 1.2.0 && < 1.6.1

range

Application

openstackredhat

1 version

Detection & mitigation playbook

Open-source dependency

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

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

In Red Hat OpenStack Platform, jolokia is not enabled by default and, when enabled, the jolokia endpoints do not rely on CORS for security. Therefore, the impact has been reduced to Low and no updates will be provided at this time for the RHOSP jolokia package.

Product	Fixed in	Advisory
Red Hat Fuse 6.3	`jolokia-core`	RHSA-2019:2804
Red Hat Fuse 7.4.0	`jolokia-core`	RHSA-2019:2413

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-10899 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works