- A GitHub advisory (GHSA-f67j-2jqw-jpq7, September 28) says one incomplete DOCTYPE snippet can make the domino HTML parser in Angular's @angular/platform-server loop forever and stop answering all requests.
- It matters because Node.js handles requests on one thread, so a frozen process hits every visitor, and the advisory says an unauthenticated remote attacker can trigger it.
- Check whether your Angular apps render on the server and pass visitor text into HTML handling. The advisory suggests showing input as plain text, or checking it and rejecting DOCTYPE-led input.
Security teams often picture attackers stealing data. This advisory describes something plainer: a website that stops answering. In Angular server-rendered apps that pass visitor text into HTML handling, one short piece of text can cause it, and no login is needed.
What the advisory says
The GitHub Advisory Database published GHSA-f67j-2jqw-jpq7 on September 28. It covers @angular/platform-server, the part of Angular that builds pages on the server. That package relies on a parser called domino to read and clean up HTML.
The flaw is triggered by an incomplete DOCTYPE declaration that ends in whitespace just before the input stops. The advisory's example is <!DOCTYPE html followed by a space. The parser then loops forever.
The advisory traces the cause to one branch of the parser's code. When it reached the end of the input, it recorded its tokens but never moved its position forward. It kept reading the same spot again and again.
One process, every visitor
The damage comes from how Node.js works. It runs page requests on a single thread. The advisory says the endless loop starves the event loop, the part that decides which request gets handled next.
Think of one cashier who stalls over a single odd coin. Everyone in the queue waits, not just the person holding the coin.
According to the advisory, the process stops responding to all current and later requests. It describes the attacker as unauthenticated and remote.
This shows that availability is a security property, and that it depends on the least careful step in the request path. A tool that cleans up HTML is meant to make a page safer. Here, one malformed input turns that step into an outage.
Who is exposed
Exposure turns on one question: does text typed by a visitor pass through the server's HTML handling? The advisory says apps that do this are reachable. It names several routes, including innerHTML bindings and server-side sanitizing.
WebPulse's September 2026 scan of the Tranco top-10,000 domains detected Angular on 155 of the 2,491 sites where a platform was identified (6.2%).
That figure shows how widely the framework was detected. It does not show how many sites are exposed. The scan cannot tell which sites render on the server, or which pass user input into HTML.
What the source does not say
The advisory text available to us gives no CVE ID, severity score or list of fixed versions. It does not report any attacks in the wild. Teams should read the full advisory for patch details.
Questions for your team this week
First, ask which of your applications use Angular server-side rendering. Second, ask where user-supplied text reaches server-side HTML handling.
Third, ask what happens when a server process hangs but does not crash. The advisory says the process stops responding. Ask whether your monitoring and restart rules would catch that.
The advisory offers two workarounds. First, keep raw visitor input out of innerHTML bindings on the server, and show it as plain text when HTML is not needed. Second, where HTML is needed, check the input beforehand and remove or reject anything that begins with a DOCTYPE declaration.
Uptime depends on every parser in the request path, including the ones nobody thinks about.
Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: GitHub Advisory Database.





