Prototype Pollution in chartkick

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

EPSS

• CVE-2019-18841: 1.39% estimated exploitation activity in the next 30 days; percentile 72.37 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Affected versions of @polymer/polymer are vulnerable to prototype pollution. The package fails to prevent modification of object prototypes through chart options containing a payload such as {"proto": {"polluted": true}}. It is possible to achieve the same results if a chart loads data from a malicious server. Recommendation Upgrade to version 3.2.0 or later.

Published by the source

2 Dec 2019, 18:04 UTC

Last modified by the source

4 Dec 2024, 05:31 UTC

Source last checked

26 Oct 2026, 12:16 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5pm8-492c-92p5

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-5pm8-492c-92p5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-18841

Advisory: Prototype Pollution in chartkick
IDs: CVE-2019-18841, GHSA-5pm8-492c-92p5
Record: https://patchnext.com/advisories/cve-2019-18841 (revision 2, source checked 26 Oct 2026, 12:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: chartkick 3.2.0; chartkick 3.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm chartkick: affected >= 3.1.0, <= 3.1.3; fixed in 3.2.0
- RubyGems chartkick: affected < 3.3.0; fixed in 3.3.0

## Suggested inspection (read-only)
- `npm ls chartkick --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- RubyGems chartkick: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on chartkick.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5pm8-492c-92p5 (OSV record GHSA-5pm8-492c-92p5 lists affected ranges: RubyGems chartkick >=0 =3.1.0 <3.2.0 (fixed))
- Verified: https://github.com/advisories/GHSA-5pm8-492c-92p5 (GitHub-reviewed advisory GHSA-5pm8-492c-92p5 lists affected ranges: RubyGems chartkick >=0 =3.1.0 <=3.1.3)

Commands are suggestions: review each one before running it.