How severe is CVE-2019-10240?

CVE-2019-10240 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-10240?

CVE-2019-10240 affects the following packages: org.eclipse.hawkbit:hawkbit-autoconfigure (Maven), org.eclipse.hawkbit:hawkbit-ui (Maven), org.eclipse.hawkbit:hawkbit-parent (Maven), org.eclipse.hawkbit:hawkbit-starters (Maven), org.eclipse.hawkbit:hawkbit-boot-starter (Maven), org.eclipse.hawkbit:hawkbit-update-server (Maven), org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui (Maven), org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api (Maven), and 2 more. Ecosystems affected: Maven.

How do I fix CVE-2019-10240?

Update org.eclipse.hawkbit:hawkbit-autoconfigure to 0.3.0M2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10240 is resolved across your whole dependency graph.

How do I detect CVE-2019-10240 in my Maven dependencies?

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

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

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

CVE-2019-10240 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th 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-2019-10240?

CVE-2019-10240 is classified as CWE-494 (CWE-494), CWE-829 (CWE-829), CWE-319 (CWE-319). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-10240 published, and has it been updated?

CVE-2019-10240 was published on April 3, 2019 and was last updated on August 13, 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-2019-10240 — hawkbit-autoconfigure

HIGH

CVE-2019-10240 is a high-severity (CVSS 8.1) CWE-494 vulnerability in org.eclipse.hawkbit:hawkbit-autoconfigure. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.eclipse.hawkbit:hawkbit-autoconfigure — see the affected versions and patch details below.

Cleartext Transmission of Sensitive Information, Inclusion of Functionality from Untrusted Control Sphere , and Download of Code Without Integrity Check in Eclipse hawkBit

Also known asGHSA-jwqm-c9f2-2cq3

Published

Apr 3, 2019

Updated

Aug 13, 2026

Affected

10 pkgs

Patched

10 / 10

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2019-10240 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

10 pkgs affected

☕org.eclipse.hawkbit:hawkbit-autoconfigure☕org.eclipse.hawkbit:hawkbit-ui☕org.eclipse.hawkbit:hawkbit-parent☕org.eclipse.hawkbit:hawkbit-starters☕org.eclipse.hawkbit:hawkbit-boot-starter☕org.eclipse.hawkbit:hawkbit-update-server☕org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-ui☕org.eclipse.hawkbit:hawkbit-boot-starter-mgmt-api+2 more

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

Eclipse hawkBit versions prior to 0.3.0M2 resolved Maven build artifacts for the Vaadin based UI over HTTP instead of HTTPS. Any of these dependent artifacts could have been maliciously compromised by a MITM attack. Hence produced build artifacts of hawkBit might be infected.

Affected Packages

10 total 10 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.hawkbit:hawkbit-autoconfigure`	all versions	0.3.0M2`org.eclipse.hawkbit:hawkbit-autoconfigure:0.3.0M2`
☕Maven	`org.eclipse.hawkbit:hawkbit-ui`	all versions	0.3.0M2`org.eclipse.hawkbit:hawkbit-ui:0.3.0M2`
☕Maven	`org.eclipse.hawkbit:hawkbit-parent`	all versions	0.3.0M2`org.eclipse.hawkbit:hawkbit-parent:0.3.0M2`
☕Maven	`org.eclipse.hawkbit:hawkbit-starters`	all versions	0.3.0M2`org.eclipse.hawkbit:hawkbit-starters:0.3.0M2`
☕Maven	`org.eclipse.hawkbit:hawkbit-boot-starter`	all versions	0.3.0M2`org.eclipse.hawkbit:hawkbit-boot-starter:0.3.0M2`
☕Maven	`org.eclipse.hawkbit:hawkbit-update-server`	all versions	0.3.0M2`org.eclipse.hawkbit:hawkbit-update-server:0.3.0M2`

Affected Products

1 product · 2 configurations

Application

hawkbiteclipse

≤ 0.2.5

1 version

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

Eclipse hawkBit versions prior to 0.3.0M2 resolved Maven build artifacts…

bugs.eclipse.orgNVDOct 2019

Detection & mitigation playbook

Open-source dependency

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

O3 Security · Impact-Aware SCA

Is CVE-2019-10240 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-494CWE-494 CWE-829CWE-829 CWE-319CWE-319

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Apr 3, 2019

First exploit

Oct 9, 2019

Last updated

Aug 13, 2026

Identifiers

CVE-2019-10240

GHSA-jwqm-c9f2-2cq3

References

Advisorynvd.nist.gov Advisorygithub.com Reportbugs.eclipse.org

Related vulnerabilities

Also affects hawkbit-parent

This CVE is high severity — higher than any of the other 1 CVE affecting hawkbit-parent (highest there: moderate).

CVE-2020-27219

Same weakness: CWE-494

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

CVE-2026-12259GHSA-xhcr-cqfr-m3hvCVE-2026-55697CVE-2026-55698GHSA-w7pm-9g55-mxfmCVE-2026-45058CVE-2026-42575Browse all CWE-494

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 13, 2026

CVE-2019-10240 — hawkbit-autoconfigure

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-2019-10240 in your dependencies?