CVE-2017-10910: MQTT.js 2.x.x prior to 2.15.0 issue in handling PUBLISH tickets may lead to an attacker causing a denial-of-se
CVE-2017-10910 is a medium-severity flaw (CVSS 6.5) affecting mqtt.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
MQTT.js 2.x.x prior to 2.15.0 issue in handling PUBLISH tickets may lead to an attacker causing a denial-of-service condition.
Why this priority
- No elevated risk signals yet
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 2.3% (top 17%) |
| CISA exploited list | No |
| Weakness | CWE-674 |
| Published | 2017-12-28 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
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-2017-10910?
mqtt.js: upgrade to 2.15.0. Exact commands for each OS are on this page.
Is CVE-2017-10910 being exploited?
CVE-2017-10910 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-2017-10910 affect?
CVE-2017-10910 affects mqtt.js. Severity is medium (CVSS 6.5). MQTT.js 2.x.x prior to 2.15.0 issue in handling PUBLISH tickets may lead to an attacker causing a denial-of-service condition.
How urgent is CVE-2017-10910?
Priority 43/100. No elevated risk signals yet.