Yayson is a library for serializing and reading JSON API data in JavaScript. Prior to 4.3.0, Store and LegacyStore use attacker-controlled JSON:API type, id, and relationship names as keys in plain-object lookup tables in src/yayson/store.ts and src/yayson/legacy-store.ts. A document whose type is __proto__ causes model-cache writes to modify Object.prototype, with the attacker controlling the polluted property name through id and its value through attributes. The malicious type can also be supplied by an included resource, and LegacyStore is reachable when a configured types mapping resolves to __proto__. Unsafe relationship names including __proto__, constructor, and prototype provide additional document-derived member paths. The resulting process-wide prototype pollution can cause denial of service and logic corruption; authorization bypass or code execution depends on suitable gadgets in the consuming application. This issue is fixed in version 4.3.0.
CVE-2026-61534
This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 45% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- 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
- 9.1
- EG Score
- 9.1(medium)
- EG Risk
- 72(Attend)EG Risk 72/100SSVC: Attend
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 computedSeverity91% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 55%
- KEV
- Not listed
Published
September 11, 2026
Last Modified
September 14, 2026
Advisory Details (3)
Auto-updated Sep 15, 2026Prototype pollution in yayson Store/LegacyStore deserialization · Advisory · confetti/yayson · GitHub
https://github.com/confetti/yayson/security/advisories/GHSA-325j-mg25-8q58Prevent prototype pollution attacks in Store and LegacyStore
Fix merged in confetti/yayson PR #111 on 2026-06-22 — awaiting tagged release
https://github.com/confetti/yayson/pull/111commit e460162d5a3e (confetti/yayson)
Fix landed in confetti/yayson commit e460162d5a3e — awaiting tagged release
https://github.com/confetti/yayson/commit/e460162d5a3ebac86424bead7424957c36f8dff9Vendor Advisories for CVE-2026-61534(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| yayson | — | 4.3.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 12× 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-09-19 18:47 UTCEG score recompute
- 2026-09-18 21:20 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:37 UTCEG score recompute
- 2026-09-16 15:43 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 07:08 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-14 20:27 UTCEG score recompute
- 2026-09-14 19:30 UTCEG score recompute
- 2026-09-14 16:26 UTCEG score recompute
- 2026-09-11 22:24 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-1321
- CVE-2020-12079EG 10.0CRITICAL
- CVE-2011-10019EG 9.8EPSS p90CRITICAL
- CVE-2020-28462NVD 7.3EG 9.8CRITICAL
- CVE-2020-28276EG 9.8CRITICAL
- CVE-2020-28271EG 9.8CRITICAL
- CVE-2020-28270EG 9.8EPSS p90CRITICAL
- CVE-2020-28269EG 9.8EPSS p90CRITICAL
- CVE-2020-8158EG 9.8CRITICAL
- CVE-2019-0230EG 9.8EPSS p100CRITICAL
- CVE-2020-7727EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-61534?
When was CVE-2026-61534 disclosed?
Is CVE-2026-61534 actively exploited?
What is the CVSS score of CVE-2026-61534?
How do I remediate CVE-2026-61534?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61534
Is Your Infrastructure Affected by CVE-2026-61534?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.