LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22775: devalue vulnerable to denial of service due to memory/CPU exhaustion in devalue.parse

Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From 5.1.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 ArrayBuffer hydration expecting base64 encoded strings as input, but not checking the assumption before decoding the input. This vulnerability is fixed in 5.6.2.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22775 is a denial-of-service flaw in Svelte's devalue library. Affected applications that pass untrusted data into devalue.parse can consume excessive CPU or memory, slowing or crashing service. The provided sources do not indicate data theft or code execution.

Executive priority

Prioritize patching internet-facing or multi-tenant services that parse user-controlled data with devalue. The main business risk is service disruption, not confirmed compromise. Treat as high priority where availability is customer-facing or operationally critical.

Technical view

devalue versions 5.1.0 through 5.6.1 fail to validate that ArrayBuffer hydration input is base64 before decoding. Malformed externally supplied parse input can trigger resource exhaustion in devalue.parse. The advisory maps this to CWE-405 and CVSS 3.1 score 7.5 with high availability impact.

Likely exposure

Exposure is limited to JavaScript applications using sveltejs/devalue >=5.1.0 and <5.6.2 that call devalue.parse on externally supplied or attacker-influenced data. Applications parsing only trusted internal data are less likely exposed based on the provided evidence.

Exploitation context

The bundle does not identify active exploitation, and KEV is false. The condition matters when an unauthenticated or low-friction user can submit data later parsed by devalue.parse. No weaponized exploit details are provided in the source bundle.

Researcher notes

The root cause is missing validation before ArrayBuffer base64 decoding during parse hydration. Evidence is strongest for upstream devalue versions 5.1.0 to before 5.6.2. The provided bundle does not prove exploit-in-the-wild activity or broaden impact beyond denial of service.

Mitigation direction

  • Upgrade devalue to 5.6.2 or later where the vulnerability is fixed.
  • Find direct and transitive dependencies that pin devalue versions before 5.6.2.
  • Restrict devalue.parse to trusted inputs until patched.
  • Monitor vendor advisories for ecosystem packages that bundle devalue.
  • Apply relevant Red Hat errata if using affected Red Hat-distributed packages.

Validation and detection

  • Inventory package lockfiles for devalue versions >=5.1.0 and <5.6.2.
  • Search code paths for devalue.parse handling request, message, or user-supplied data.
  • Confirm deployed builds include devalue 5.6.2 or later.
  • Review service monitoring for CPU or memory spikes around parsing endpoints.
  • Check Red Hat CVE and errata pages for product-specific status.
Prepared
Confidence
high
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-405: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22775 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6GitHub_M
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-22775Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPdevalue: devalue: Denial of Service due to improper input validation
other:Red Hat severity ratingcvssV3_1
  • 2026-01-15T20:00:50.600Z: Reported to Red Hat.
  • 2026-01-15T18:59:37.499Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
sveltejsdevalue>= 5.1.0, < 5.6.2Listed
Weakness

CWE details

CWE-405

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-405 · source CWE mapping

Asymmetric Resource Consumption (Amplification)

Asymmetric Resource Consumption (Amplification) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs