Skip to main content
HIGH

CVE-2026-22774

CVSS v3

7.5

HIGH

EPSS Score

0.6 %

exploit probability, as of 2026-10-19

CISA KEV

No

known exploited

Exploitation

—

SSVC status

Get an alert for each new CVE published for devalue.

Set up CVE WatchFree account · no credit card

Affected and fixed versions

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • devaluenpmfrom 5.3.0 · fixed in 5.6.2

Vendor advisories

  • CVE-2026-22774 Red Hat Product Security2 products fixed · 1 known affected

    devalue: devalue: Denial of Service due to excessive resource consumption from untrusted input

    rhdesktop/rh-podman-desktop-ext-bootc-rhel10 as a component of Red Hat Build of Podman Desktop - Tech Preview

  • RHSA-2026:2926 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: RHTAS 1.2.2 - Red Hat Trusted Artifact Signer Release

  • RHSA-2026:2144 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: RHTAS 1.3.2 - Red Hat Trusted Artifact Signer Release

Full record on NVD

Description

Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From 5.3.0 to 5.6.1, certain inputs can cause devalue.parse to consume excessive CPU time and/or memory, potentially leading to denial of service in systems that parse input from untrusted sources. This affects applications using devalue.parse on externally-supplied data. The root cause is the typed array hydration expecting an ArrayBuffer as input, but not checking the assumption before creating the typed array. This vulnerability is fixed in 5.6.2.

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2026-01-15
Last Modified
2026-01-20

Frequently asked questions

What is CVE-2026-22774?

Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From 5.3.0 to 5.6.1, certain inputs can cause devalue.parse to consume excessive CPU time and/or memory, potentially leading to denial of service in systems that parse input from untrusted sources. This affects applications using devalue.parse on externally-supplied data. The root cause is the typed array hydration expecting an ArrayBuffer as input, but not checking the assumption before creating the typed array. This vulnerability is fixed in 5.6.2.

Is CVE-2026-22774 actively exploited?

Active exploitation of CVE-2026-22774 has not been confirmed. Its EPSS score was 0.6% on 2026-10-19, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-22774?

CVE-2026-22774 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running devalue? Hear about its next vulnerability

CVE Watch matches each new CVE to the vendors and products you list (vendor and product, not the version) and puts it in your alerts with its KEV and EPSS status.

Get alerts for this productCISA KEV additions, October 2026Search CVEs

Already have an account? Open CVE WatchNo credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database