VulnerabilityPublished 13 Oct 2026Updated 28 Oct 2026

CVE-2026-109149: Node js beautify · A weakness has been identified in beautifier js-beautify up to 1.15.1/2.0.3

Affects node-js-beautifySource GCVE Database

Authoritative record:CVE-2026-109149· Medium 6.9

Public exploit available · CVSS 6.9 Medium.

Data as of 29 Oct 2026, 00:42 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10node-js-beautify`pkg:deb/ubuntu/node-js-beautify?arch=source&distro=stonking`Other threats	Affected =1.15.4+dfsg+~cs1.31.6-1 =1.15.4+dfsg+~cs1.31.6-3	Fixed in–
Ubuntu 26.04 LTSnode-js-beautify`pkg:deb/ubuntu/node-js-beautify?arch=source&distro=resolute`Other threats	Affected =1.15.4+dfsg+~cs1.31.6-1	Fixed in–
Ubuntu 24.04 LTSnode-js-beautify`pkg:deb/ubuntu/node-js-beautify?arch=source&distro=noble`Other threats	Affected =1.14.7+dfsg+~cs1.28.6-1	Fixed in–
Ubuntu 22.04 LTSnode-js-beautify`pkg:deb/ubuntu/node-js-beautify?arch=source&distro=jammy`Other threats	Affected =1.13.6+dfsg+~0.15.3-1 =1.14.0+dfsg+~0.15.3-1	Fixed in–
Ubuntu 20.04 LTSnode-js-beautify`pkg:deb/ubuntu/node-js-beautify?arch=source&distro=focal`Other threats	Affected =1.10.2+dfsg-1 =1.10.3+dfsg-1	Fixed in–
Ubuntu 18.04 LTSnode-js-beautify`pkg:deb/ubuntu/node-js-beautify?arch=source&distro=bionic`Other threats	Affected =1.7.5+dfsg-1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor for vendor advisories for any future patches. Until a fix is released, consider limiting exposure of the affected service to untrusted networks to reduce risk.

Description

A vulnerability exists in the Node.js package js-beautify up to versions 1.15.1 and 2.0.3. The flaw involves an unknown function that can be manipulated to cause uncontrolled memory allocation. This issue can be exploited remotely and results in a denial of service condition due to resource exhaustion. The vendor was contacted but did not provide a response or patch at the time of disclosure.

Impact

The vulnerability allows remote attackers to cause uncontrolled memory allocation, leading to denial of service (availability impact). There is no impact on confidentiality or integrity reported. No known exploits are currently in the wild.

Summary

The js-beautify Node.js package versions up to 1.15.1 and 2.0.3 contain a weakness in an unspecified function that allows an attacker to trigger uncontrolled memory allocation remotely. This vulnerability can lead to denial of service by exhausting system memory. No vendor response or patch has been provided as of the disclosure date.

References

Community reviews

Loading reviews…