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.
CVE-2026-78181
Score 7.3 from GitHub Security Advisory published 2026-08-24. a secondary CVSS source baseline 7.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(high)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity73% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 36%
- KEV
- Not listed
Published
August 24, 2026
Last Modified
August 24, 2026
Advisory Details (2)
Auto-updated Aug 24, 2026GitHub - ractivejs/ractive: Next-generation DOM manipulation · GitHub
https://github.com/ractivejs/ractive/Prototype pollution in keypath setters enables cross-instance template/data injection · Issue #3448 · ractivejs/ractive · GitHub
https://github.com/ractivejs/ractive/issues/3448Vendor Advisories for CVE-2026-78181(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 13× in last 7d / 13× 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-08-26 14:47 UTCEPSS rescore
- 2026-08-26 05:22 UTCGHSA enrichment
- 2026-08-25 17:11 UTCEG score recompute
- 2026-08-25 17:10 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 04:59 UTCGHSA enrichment
- 2026-08-24 16:46 UTCEG score recompute
- 2026-08-24 16:46 UTCGHSA enrichment
- 2026-08-24 14:18 UTCEPSS rescore
- 2026-08-24 04:23 UTCEG score recompute
- 2026-08-24 04:21 UTCNVD updateCVSS v4 → 5.5
- 2026-08-24 03:51 UTCEG score recompute
- 2026-08-24 03:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-94
- CVE-2003-1432EG 10.0EPSS p94HIGH
- CVE-2002-0495EG 10.0EPSS p96HIGH
- CVE-1999-0702EG 10.0EPSS p98HIGH
- CVE-1999-0509EG 10.0EPSS p98HIGH
- CVE-2006-1318EG 9.3EPSS p97HIGH
- CVE-2006-1301EG 9.3EPSS p95HIGH
- CVE-2006-1308EG 9.3EPSS p95HIGH
- CVE-2006-1309EG 9.3EPSS p95HIGH
- CVE-2006-1304EG 9.3EPSS p96HIGH
- CVE-2006-1306EG 9.3EPSS p95HIGH
Frequently asked(5)
What is CVE-2026-78181?
When was CVE-2026-78181 disclosed?
Is CVE-2026-78181 actively exploited?
What is the CVSS score of CVE-2026-78181?
How do I remediate CVE-2026-78181?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78181
Is Your Infrastructure Affected by CVE-2026-78181?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.