CVE-2026-109149 beautifier CVE debrief

Who should care

Defenders responsible for js-beautify deployments should assess exposure and prioritize verification of affected versions. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is is

Why it matters

Defenders should assess exposure and prioritize verification of affected js-beautify versions due to a weakness allowing uncontrolled memory allocation.

• Verify affected versions and prioritize remediation
• Monitor for potential exploitation attempts
• Assess exposure of js-beautify versions up to 1.15.1/2.0.3

Technical summary

The beautifier js-beautify library up to versions 1.15.1/2.0.3 contains a weakness that allows for uncontrolled memory allocation. This can be exploited remotely via an unknown function. The vulnerability may lead to memory corruption and system instability. Defenders should assess exposure, prioritize verification of affected versions, and monitor for potential exploitation. The vendor was contacted early about this disclosure but did not respond in any way. This issue requires immediate attention from defenders responsible for js-beautify deployments.

Defensive priority

Defenders should assess exposure, prioritize verification of affected versions, and monitor for potential exploitation.

Recommended defensive actions

• Assess exposure of js-beautify versions up to 1.15.1/2.0.3
• Verify affected versions and prioritize remediation
• Monitor for potential exploitation attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide limited information about the vulnerability, affected versions, and potential impact. The CVE record was published on 2026-10-13T09:30:16.051Z and has not been modified since then. The source item provides CVE metadata but lacks detailed information on the vulnerability. No additional sources were provided to supplement this information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.