GHSA-58w9-8g37-x9v5
MEDIUMGHSA-58w9-8g37-x9v5 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in @angular/compiler. O3 Security confirms whether GHSA-58w9-8g37-x9v5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
@angular/compiler: Two-Way Property Binding Sanitization Bypass (XSS)
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@angular/compilernpmDescription
An issue in the @angular/compiler package allows bypassing DOM property sanitization through the use of two-way property bindings.
Specifically, when a native DOM property that requires sanitization (such as innerHTML, srcdoc, src, href, data, or sandbox) is bound using the two-way binding syntax (e.g., [(innerHTML)]="value" or bindon-innerHTML="value"), the Angular template compiler failed to apply the appropriate schema-derived sanitizer resolution to the TwoWayProperty operation. As a result, native two-way DOM bindings were emitted without the required sanitizer function, whereas equivalent one-way bindings would be properly sanitized.
This flaw enables an attacker who can control the value of a two-way bound sensitive property to bypass Angular's built-in sanitization logic, potentially leading to client-side Cross-Site Scripting (XSS).
Impact
Any Angular application that uses two-way data binding ([()] or bindon-) on security-sensitive native DOM properties (like innerHTML, href on <a>, src on <img>/<iframe>, etc.) is vulnerable to this security bypass.
Once exploited, this allows a malicious actor to supply an unsanitized property binding value that bypasses core sanitization constraints. This could lead to the execution of arbitrary JavaScript within the target user's browser context, potentially resulting in session hijacking, sensitive data exposure, or unauthorized actions on behalf of the user.
Attack Preconditions
To successfully exploit this vulnerability, the following environment parameters and application states must concurrently exist:
- Two-Way Binding on Sensitive Properties: The application must bind to a sensitive native DOM property using the two-way binding syntax (e.g.,
<div [(innerHTML)]="userContent"></div>). - User-Controlled Input: The value bound to this property must be influenceable by user-controlled input.
- Absence of Additional Sanitization: The application does not perform separate manual sanitization (e.g., via
DomSanitizer) before passing the value to the bound property.
Patches
- 22.0.1
- 21.2.17
- 20.3.25
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @angular/compiler | ≥ 22.0.0-next.0&&< 22.0.1 | 22.0.1 |
| 📦npm | @angular/compiler | ≥ 21.0.0-next.0&&< 21.2.17 | 21.2.17 |
| 📦npm | @angular/compiler | ≥ 20.0.0-next.0&&< 20.3.25 | 20.3.25 |
| 📦npm | @angular/compiler | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @angular/compiler. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @angular/compiler to 22.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-58w9-8g37-x9v5 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 pinpoints whether GHSA-58w9-8g37-x9v5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-58w9-8g37-x9v5. 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-58w9-8g37-x9v5 in your dependencies?
O3 detects GHSA-58w9-8g37-x9v5 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.