CVE-2026-16151

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreHIGH confidence

Score 6.3 from GitHub Security Advisory published 2026-07-18. a secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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 computed
Severity63% × 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, 2026
No patch confirmed yet.
generic

GitHub - CartoDB/carto-api-client: Client library for CARTO APIs and framework-agnostic CARTO + deck.gl applications. · GitHub

https://github.com/CartoDB/carto-api-client/
generic

Prototype pollution in `addFilter()` via `__proto__` column · Issue #299 · CartoDB/carto-api-client · GitHub

https://github.com/CartoDB/carto-api-client/issues/299

Vendor 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.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:05 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-20 17:51 UTCEG score recompute
  5. 2026-07-20 17:50 UTCGHSA enrichment
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-18 22:05 UTCEG score recompute
  9. 2026-07-18 22:05 UTCGHSA enrichment
  10. 2026-07-18 20:00 UTCEG score recompute
  11. 2026-07-18 19:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16151?
CVE-2026-16151 is a medium vulnerability published on July 18, 2026. 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…
When was CVE-2026-16151 disclosed?
CVE-2026-16151 was first published in the National Vulnerability Database on July 18, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16151 actively exploited?
CVE-2026-16151 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-16151?
CVE-2026-16151 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-16151?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16151, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16151

Explore →

Is Your Infrastructure Affected by CVE-2026-16151?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.