Skip to content

Commit b2f8f68

Browse files
1 parent 09a54a1 commit b2f8f68

5 files changed

Lines changed: 100 additions & 7 deletions

File tree

advisories/github-reviewed/2021/10/GHSA-pjwm-rvh2-c87w/GHSA-pjwm-rvh2-c87w.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@
102102
],
103103
"database_specific": {
104104
"cwe_ids": [
105-
"CWE-829",
105+
"CWE-506",
106106
"CWE-912"
107107
],
108108
"severity": "HIGH",

advisories/github-reviewed/2026/06/GHSA-58w9-8g37-x9v5/GHSA-58w9-8g37-x9v5.json

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,18 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-58w9-8g37-x9v5",
4-
"modified": "2026-06-15T17:22:40Z",
4+
"modified": "2026-07-15T22:03:42Z",
55
"published": "2026-06-15T17:22:40Z",
66
"aliases": [
77
"CVE-2026-54265"
88
],
99
"summary": "@angular/compiler: Two-Way Property Binding Sanitization Bypass (XSS)",
1010
"details": "An issue in the `@angular/compiler` package allows bypassing DOM property sanitization through the use of two-way property bindings.\n\nSpecifically, 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.\n\nThis 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).\n\n### Impact\nAny 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.\n\nOnce 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.\n\n### Attack Preconditions\nTo successfully exploit this vulnerability, the following environment parameters and application states must concurrently exist:\n1. **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>`).\n2. **User-Controlled Input:** The value bound to this property must be influenceable by user-controlled input.\n3. **Absence of Additional Sanitization:** The application does not perform separate manual sanitization (e.g., via `DomSanitizer`) before passing the value to the bound property.\n\n### Patches\n* 22.0.1\n* 21.2.17\n* 20.3.25",
1111
"severity": [
12+
{
13+
"type": "CVSS_V3",
14+
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"
15+
},
1216
{
1317
"type": "CVSS_V4",
1418
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N"
@@ -97,6 +101,10 @@
97101
"type": "WEB",
98102
"url": "https://github.com/angular/angular/security/advisories/GHSA-58w9-8g37-x9v5"
99103
},
104+
{
105+
"type": "ADVISORY",
106+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-54265"
107+
},
100108
{
101109
"type": "WEB",
102110
"url": "https://github.com/angular/angular/pull/69107"
@@ -117,6 +125,6 @@
117125
"severity": "MODERATE",
118126
"github_reviewed": true,
119127
"github_reviewed_at": "2026-06-15T17:22:40Z",
120-
"nvd_published_at": null
128+
"nvd_published_at": "2026-06-22T16:16:39Z"
121129
}
122130
}

advisories/github-reviewed/2026/06/GHSA-692r-grfm-v8x7/GHSA-692r-grfm-v8x7.json

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,18 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-692r-grfm-v8x7",
4-
"modified": "2026-06-15T16:51:36Z",
4+
"modified": "2026-07-15T22:03:32Z",
55
"published": "2026-06-15T16:51:35Z",
66
"aliases": [
77
"CVE-2026-52725"
88
],
99
"summary": "@angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)",
1010
"details": "An issue in the `@angular/core` package allows bypassing script-execution restrictions during dynamic component creation.\n\nSpecifically, the dynamic component instantiation mechanism (`createComponent`) failed to reject mounting components directly onto a `<script>` or namespaced script element (such as `<svg:script>`). This enabled the initialization of custom components on a tag that executes scripts, allowing attackers to hijack or inject script-executing hosts.\n\nThis flaw enables an attacker who can control the host element or selector parameter passed to `createComponent` to initialize or mount an Angular component directly onto a `<script>` tag, leading to execution of untrusted code or client-side Cross-Site Scripting (XSS).\n\n### Impact\nAny Angular application that registers dynamic components based on user-supplied parameters (like selectors or host elements) is vulnerable to this security bypass.\n\nOnce exploited, this allows a malicious actor to mount a dynamic component on a script tag, bypassing core dynamic component creation safeguards to execute arbitrary JavaScript within the target user's browser context. This could lead to session hijacking, sensitive data exposure, or unauthorized actions on behalf of the user.\n\n### Attack Preconditions\nTo successfully exploit these vulnerabilities, the following environment parameters and application states must all concurrently exist:\n1. **User-Controlled Host Selection:** The application must accept user-controlled inputs that are passed as a selector/host element to `createComponent`.\n2. **Absence of Additional Context Sanitization:** The application does not perform separate input sanitization before feeding values to the dynamic creation APIs.\n\n### Patches\n* 22.0.0-rc.2\n* 21.2.15\n* 20.3.22\n* 19.2.23",
1111
"severity": [
12+
{
13+
"type": "CVSS_V3",
14+
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"
15+
},
1216
{
1317
"type": "CVSS_V4",
1418
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N"
@@ -119,6 +123,10 @@
119123
"type": "WEB",
120124
"url": "https://github.com/angular/angular/security/advisories/GHSA-692r-grfm-v8x7"
121125
},
126+
{
127+
"type": "ADVISORY",
128+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-52725"
129+
},
122130
{
123131
"type": "WEB",
124132
"url": "https://github.com/angular/angular/pull/68686"
@@ -139,6 +147,6 @@
139147
"severity": "MODERATE",
140148
"github_reviewed": true,
141149
"github_reviewed_at": "2026-06-15T16:51:35Z",
142-
"nvd_published_at": null
150+
"nvd_published_at": "2026-06-22T16:16:38Z"
143151
}
144152
}

advisories/github-reviewed/2026/06/GHSA-f3m7-gqxr-g87x/GHSA-f3m7-gqxr-g87x.json

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,18 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-f3m7-gqxr-g87x",
4-
"modified": "2026-06-15T17:21:58Z",
4+
"modified": "2026-07-15T22:03:38Z",
55
"published": "2026-06-15T17:21:58Z",
66
"aliases": [
77
"CVE-2026-50557"
88
],
99
"summary": "Angular: Template and Attribute Namespace Sanitization Bypass (XSS)",
1010
"details": "An issue in the `@angular/compiler` and `@angular/core` packages allows bypassing element and attribute sanitization/validation through specific namespace workarounds.\n\nSpecifically, namespaced script elements (e.g., `<svg:script>` or `<:svg:script>`) were not properly identified as script elements by the Angular template preparser, allowing them to pass through template compilation without being stripped.\n\nFurthermore, security context schema mappings for element attributes did not consistently handle attributes within namespaced elements (like SVG and MathML), opening up gaps where malicious namespaced attributes could bypass runtime and compile-time sanitizers.\n\nCombined, these flaws enable an attacker who can inject or supply a template/tag structure with custom namespaces to bypass Angular's script-stripping logic and attribute sanitizers, leading to client-side Cross-Site Scripting (XSS).\n\n### Impact\nAny Angular application that compiles user-controlled templates at runtime, or relies on sanitization of namespaced elements/attributes, is vulnerable to this security bypass.\n\nOnce exploited, this allows a malicious actor to inject a namespaced script element or dynamic attribute bindings, bypassing core sanitization constraints to execute arbitrary JavaScript within the target user's browser context. This could lead to session hijacking, sensitive data exposure, or unauthorized actions on behalf of the user.\n\n### Attack Preconditions\nTo successfully exploit these vulnerabilities, the following environment parameters and application states must all concurrently exist:\n1. **User-Controlled Template Input:** The application must accept user-controlled inputs that are directly processed by the Angular template compiler at runtime.\n2. **Namespace Parsing Support:** The input structure must employ custom namespace prefixes (such as `<svg:script>`) to evade standard tag-name blocklists/checks.\n3. **Absence of Additional Context Sanitization:** The application does not perform separate input sanitization before feeding values to the Angular compiler.\n\n### Patches\n* 22.0.0-rc.2\n* 21.2.15\n* 20.3.22\n* 19.2.23",
1111
"severity": [
12+
{
13+
"type": "CVSS_V3",
14+
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"
15+
},
1216
{
1317
"type": "CVSS_V4",
1418
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N"
@@ -211,6 +215,10 @@
211215
"type": "WEB",
212216
"url": "https://github.com/angular/angular/security/advisories/GHSA-f3m7-gqxr-g87x"
213217
},
218+
{
219+
"type": "ADVISORY",
220+
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-50557"
221+
},
214222
{
215223
"type": "WEB",
216224
"url": "https://github.com/angular/angular/pull/68689"
@@ -231,6 +239,6 @@
231239
"severity": "MODERATE",
232240
"github_reviewed": true,
233241
"github_reviewed_at": "2026-06-15T17:21:58Z",
234-
"nvd_published_at": null
242+
"nvd_published_at": "2026-06-22T16:16:38Z"
235243
}
236244
}
Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-ghhp-3qvg-889p",
4+
"modified": "2026-07-15T22:01:52Z",
5+
"published": "2026-07-15T22:01:52Z",
6+
"aliases": [
7+
"CVE-2026-54463"
8+
],
9+
"summary": "websocket-driver: Memory exhaustion via abuse of protocol length headers",
10+
"details": "### Impact\n\nThe frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values `0x80` or above, a server or client can make the other peer parse these bytes into an ever-growing integer. Since Ruby integers are arbitrary precision, this can be used to make a WebSocket connection consume an unbounded amount of memory and lead to the host process running out of memory.\n\n### Patches\n\nThe issue has been patched in version 0.8.1. All users should upgrade to this version.\n\n### Workarounds\n\nNo known workarounds exist.\n\n### Acknowledgements\n\nThis issue was discovered and reported by Pranjali Thakur, DepthFirst Security Research Team.",
11+
"severity": [
12+
{
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "RubyGems",
21+
"name": "websocket-driver"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "0"
29+
},
30+
{
31+
"fixed": "0.8.1"
32+
}
33+
]
34+
}
35+
]
36+
}
37+
],
38+
"references": [
39+
{
40+
"type": "WEB",
41+
"url": "https://github.com/faye/websocket-driver-ruby/security/advisories/GHSA-ghhp-3qvg-889p"
42+
},
43+
{
44+
"type": "PACKAGE",
45+
"url": "https://github.com/faye/websocket-driver-ruby"
46+
},
47+
{
48+
"type": "WEB",
49+
"url": "https://github.com/faye/websocket-driver-ruby/releases/tag/0.8.1"
50+
},
51+
{
52+
"type": "WEB",
53+
"url": "https://github.com/rubysec/ruby-advisory-db/blob/master/gems/websocket-driver/CVE-2026-54463.yml"
54+
},
55+
{
56+
"type": "WEB",
57+
"url": "https://www.cve.org/CVERecord/SearchResults?query=CVE-2026-54463"
58+
}
59+
],
60+
"database_specific": {
61+
"cwe_ids": [
62+
"CWE-400"
63+
],
64+
"severity": "MODERATE",
65+
"github_reviewed": true,
66+
"github_reviewed_at": "2026-07-15T22:01:52Z",
67+
"nvd_published_at": null
68+
}
69+
}

0 commit comments

Comments
 (0)