Skip to content
Web

CVE-2026-23929

8.5
High
EPSS 0.18%Patch availableAug 18, 2026

Prototype pollution in searchParamsToObject enables persistent XSS in Maps.

common questions

Is CVE-2026-23929 being exploited?

Not confirmed. CVE-2026-23929 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.

How severe is CVE-2026-23929?

CVE-2026-23929 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-23929?

Yes. A fix has been recorded for CVE-2026-23929. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-23929 affect?

CVE-2026-23929 affects Maps components using searchParamsToObject(), Web applications that parse untrusted URL params into objects, Libraries using jQuery element creation that traverses prototype chain. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-23929?

Sanitize URL params, block '__proto__', and apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Maps components using searchParamsToObject()Web applications that parse untrusted URL params into objectsLibraries using jQuery element creation that traverses prototype chain
impact

Persistent XSS via prototype pollution in searchParamsToObject; attackers can execute JS in victims' browsers, steal cookies/tokens, and act as users.

action required

Patch when possible

affected versions
Zabbix Zabbix
  • affected>= 6.0.44 and <= 6.0.45
  • affected>= 7.0.22 and <= 7.0.24
  • affected>= 7.4.6 and <= 7.4.8

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free