hawtio before version 1.5.5 is vulnerable to remote code execution via file upload.

published 2018-05-22 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-11778

cvss: 7.6; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.7%; EPSS 1.7% chance of exploitation in 30 days, percentile 76%
public exploits: 0; none known

hawtio before version 1.5.5 is vulnerable to remote code execution via file upload. An attacker could use this vulnerability to upload a crafted file which could be executed on a target machine where hawtio is deployed.

Patch / fix

fixed in 1

hawt hawtio 1.5.5

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-2617 updated 2026-06-30 cvss 7.6

Hawtio: Unrestricted file upload leads to RCE

Red Hat JBoss A-MQ 6 hawtio hawtio Red Hat JBoss Fuse 6 hawtio hawtio
affected: no fix planned “Out of support scope”
Red Hat OpenShift Enterprise 2 hawtio
under investigation
Red Hat JBoss A-MQ 6.3 Red Hat JBoss Fuse 6.3
fixed: vendor fix RHSA-2018:0319

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.65% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	7.6	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
NVD	3.0	7.8	CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

[UNKNOWN] hawtio

Classification

Weakness

CWE-20 Improper Input Validation
CWE-434 Unrestricted Upload of File with Dangerous Type

References

access.redhat.com /errata/RHSA-2018:0319
vendor-advisory, third-party-advisory
bugzilla.redhat.com /show_bug.cgi?id=CVE-2017-2617
issue-tracking, third-party-advisory
securityfocus.com /bid/96036
vdb-entry, third-party-advisory

Sources

CVE List CVE-2017-2617
NVD CVE-2017-2617

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary