A vulnerability has been found in CartoDB carto-api-client 0.5.29. This impacts the function addFilter of the file src/filters.ts. Such manipulation of the argument column leads to improperly controlled modification of object prototype attributes. The attack can be executed remotely. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-16151
Score 6.3 from GitHub Security Advisory published 2026-07-18. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 24.3%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 20, 2026
Advisory Details (2)
Auto-updated Jul 18, 2026GitHub - CartoDB/carto-api-client: Client library for CARTO APIs and framework-agnostic CARTO + deck.gl applications. · GitHub
https://github.com/CartoDB/carto-api-client/Prototype pollution in `addFilter()` via `__proto__` column · Issue #299 · CartoDB/carto-api-client · GitHub
https://github.com/CartoDB/carto-api-client/issues/299Vendor Advisories for CVE-2026-16151(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-20 17:51 UTCEG score recompute
- 2026-07-20 17:50 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 22:05 UTCEG score recompute
- 2026-07-18 22:05 UTCGHSA enrichment
- 2026-07-18 20:00 UTCEG score recompute
- 2026-07-18 19:59 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-94
Frequently asked(5)
What is CVE-2026-16151?
When was CVE-2026-16151 disclosed?
Is CVE-2026-16151 actively exploited?
What is the CVSS score of CVE-2026-16151?
How do I remediate CVE-2026-16151?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16151
Is Your Infrastructure Affected by CVE-2026-16151?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.