CVE-2019-18841: Chartkick.js 3.1.0 through 3.1.3, as used in the Chartkick gem before 3.3.0 for Ruby, allows prototype polluti
CVE-2019-18841 is a high-severity flaw (CVSS 7.3) affecting chartkick.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Chartkick.js 3.1.0 through 3.1.3, as used in the Chartkick gem before 3.3.0 for Ruby, allows prototype pollution.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.3 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.4% (top 28%) |
| CISA exploited list | No |
| Published | 2019-11-11 |
| 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-2019-18841?
chartkick.js: upgrade to newer than 3.1.3. Exact commands for each OS are on this page.
Is CVE-2019-18841 being exploited?
CVE-2019-18841 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-2019-18841 affect?
CVE-2019-18841 affects chartkick.js. Severity is high (CVSS 7.3). Chartkick.js 3.1.0 through 3.1.3, as used in the Chartkick gem before 3.3.0 for Ruby, allows prototype pollution.
How urgent is CVE-2019-18841?
Priority 49/100. High severity; Remotely exploitable, no login, no user action