Is mqtt 0.3 vulnerable?
RubyGems · 2 releases from 0.3.0 to 0.3.1 · latest mqtt is 0.7.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. mqtt 0.3.1, the last 0.3 release, is affected by 1 known security advisory (1 high), including CVE-2025-12790. Upgrade to 0.7.0 or later to fix all of them.
bundle update --conservative mqtt # Gemfile: '>= 0.7.0'Is your project on an affected mqtt?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting mqtt 0.3.1
MQTT does not validate hostnames
- Affected
- <0.7.0
- Fixed in
- 0.7.0
Every mqtt 0.3.x release
Affected: 0.3.0 to 0.3.1. Latest mqtt: 0.7.0.
| Version | Known advisories |
|---|---|
| mqtt 0.3.1 | CVE-2025-12790 |
| mqtt 0.3.0 | CVE-2025-12790 |
Which of your client projects are still on mqtt 0.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact mqtt version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other mqtt versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.