What is CVE-2026-16151?
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.
The record classifies CVE-2026-16151 under weakness classes CWE-1321, CWE-94. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 79 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 6.3 — MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:X/RL:X/RC:R - CVSS v4.0 base score
- 5.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X - EPSS (FIRST)
- 0.3% probability of exploitation in the next 30 days, higher than 24.1% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 4.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-07-18
Is CVE-2026-16151 being exploited?
It currently carries a trending score of 36 in the Threadlinqs vulnerability feed.
Affected products and versions
- CartoDB: carto-api-client
How to fix CVE-2026-16151
No vendor patch reference has been recorded for CVE-2026-16151 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-16151
No threat campaign in the Threadlinqs corpus currently references CVE-2026-16151, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on .