GHSA-r3hf-q8q7-fv2p — @nguniversal/common
GHSA-r3hf-q8q7-fv2p is a security vulnerability in @nguniversal/common. A fix is available for @nguniversal/common — see the affected versions and patch details below.
Angular critical CSS inlining Cross-site Scripting Vulnerability Advisory
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@nguniversal/commonnpmDescription
Impact
Angular Universal applications on 16.1.0 and 16.1.1 using critical CSS inlining are vulnerable to a cross-site scripting (XSS) attack where an attacker can trick another user into visiting a page which injects malicious JavaScript.
Angular CLI applications without Universal do perform critical CSS inlining as well, however exploiting this requires a malicious actor to already have access to modify source code directly.
Patches
@nguniversal/common should be upgraded to 16.1.2 or higher. 16.2.0-rc.0 is safe.
Workarounds
The easiest solution is likely to upgrade Universal to 16.1.2 or downgrade to 16.0.x or lower. Alternatively you can override specifically the critters dependency with version 0.0.20 in your package.json.
{
"overrides": {
"critters": "0.0.20"
}
}
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @nguniversal/common | ≥ 16.1.0&&< 16.1.2 | 16.1.2npm install @nguniversal/common@16.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @nguniversal/common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @nguniversal/common to 16.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r3hf-q8q7-fv2p is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r3hf-q8q7-fv2p can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r3hf-q8q7-fv2p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-r3hf-q8q7-fv2p in your dependencies?
O3 Security finds GHSA-r3hf-q8q7-fv2p across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.