CVE-2018-15531: JavaMelody before 1.74.0 has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.

Q: How do I fix CVE-2018-15531?

javamelody: upgrade to 1.74.0. Exact commands for each OS are on this page.

Q: Is CVE-2018-15531 being exploited?

CVE-2018-15531 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-15531 affect?

CVE-2018-15531 affects javamelody. Severity is critical (CVSS 9.8). JavaMelody before 1.74.0 has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.

Q: How urgent is CVE-2018-15531?

Priority 64/100. Critical severity; EPSS top 2%: very likely to be exploited; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2018-15531 is a critical-severity flaw (CVSS 9.8) affecting javamelody. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

JavaMelody before 1.74.0 has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.

Why this priority

Critical severity
EPSS top 2%: very likely to be exploited
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	27.9% (top 2%)
CISA exploited list	No
Weakness	CWE-611
Published	2018-09-26
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: javamelody project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-09-26 22:29 UTCPublished CVE record published
2026-06-17 01:42 UTCUpdated Record last modified

javamelody project javamelody UPGRADE

Affected: < 1.74.0

Fixed in: 1.74.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy javamelody || rpm -q javamelody || javamelody --version

2. UPGRADE to 1.74.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade javamelody

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade javamelody

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-15531?

javamelody: upgrade to 1.74.0. Exact commands for each OS are on this page.

Is CVE-2018-15531 being exploited?

CVE-2018-15531 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-15531 affect?

CVE-2018-15531 affects javamelody. Severity is critical (CVSS 9.8). JavaMelody before 1.74.0 has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.

How urgent is CVE-2018-15531?

Priority 64/100. Critical severity; EPSS top 2%: very likely to be exploited; Remotely exploitable, no login, no user action

Software pages

Java vulnerabilities

Related CVEs

CVE-2018-12432 MEDIUM 6.1 UPGRADE JavaMelody through 1.60.0 has XSS via the counter parameter in a clear_counter action to the /monitoring URI.

References

← Back to latest CVEs