CVE & CISA-KEV Catalog

CVE-2026-61534

CRITICAL
9.1
CVSS v3
NVD

Description

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.

How to fix

Remediation Available
yaysonnpm
Fixed in:4.3.0GHSA-325j-mg25-8q58

TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityHigh
AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Exploit Intelligence

0.78%probability of exploitation in 30 days
54thpercentile

Moderate risk: more likely to be exploited than 54% of all known CVEs.

References

Related Vulnerabilities

Other CWE-1321 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2019-0230Critical9.897%--
CVE-2019-11358Medium6.187%-Fix
CVE-2020-7774High7.369%-Fix
CVE-2022-24760Critical10.049%-Fix
CVE-2022-39396Critical9.839%-Fix
CVE-2022-2564Critical9.833%-Fix

Common questions

How do I fix CVE-2026-61534?

Upgrade yayson to 4.3.0 or later.

Is CVE-2026-61534 being actively exploited?

Not that we know of. CVE-2026-61534 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.78% is the estimated probability that it will be exploited in the next 30 days. That is higher than 54% of all scored CVEs.

How severe is CVE-2026-61534?

CVE-2026-61534 has a CVSS v3 base score of 9.1, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

What does CVE-2026-61534 affect?

Published advisories record a fix for yayson (npm). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.

Embed a live status badge for CVE-2026-61534
CVE-2026-61534 severity badge

Markdown

[![CVE-2026-61534](https://tridentstack.com/cve/badge/CVE-2026-61534.svg)](https://tridentstack.com/cve/CVE-2026-61534)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-61534"><img src="https://tridentstack.com/cve/badge/CVE-2026-61534.svg" alt="CVE-2026-61534"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-14.