Skip to content

Commit 452bb8b

Browse files
1 parent e3031e6 commit 452bb8b

2 files changed

Lines changed: 127 additions & 0 deletions

File tree

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-6738-r8g5-qwp3",
4+
"modified": "2026-01-15T20:13:33Z",
5+
"published": "2026-01-15T20:13:33Z",
6+
"aliases": [
7+
"CVE-2025-15265"
8+
],
9+
"summary": "svelte vulnerable to Cross-site Scripting",
10+
"details": "## Summary\n\nAn XSS vulnerability exists in Svelte 5.46.0-2 resulting from improper escaping of `hydratable` keys. If these keys incorporate untrusted user input, arbitrary JavaScript can be injected into server-rendered HTML.\n\n## Details\n\nWhen using the [`hydratable`](https://svelte.dev/docs/svelte/hydratable) function, the first argument is used as a key to uniquely identify the data, such that the value is not regenerated in the browser.\n\nThis key is embedded into a `<script>` block in the server-rendered `<head>` without escaping unsafe characters. A malicious key can break out of the script context and inject arbitrary JavaScript into the HTML response.\n\n## Impact\n\nThis is a cross-site scripting vulnerability affecting applications that have the `experimental.async` flag enabled and use `hydratable` with keys incorporating untrusted user input. \n\n- **Impact**: Arbitrary JS execution in the client’s browser.\n- **Exploitability**: Remote, single-request if key is attacker-controlled.\n- **Typical Outcomes**:\n - Session/token theft\n - DOM defacement\n - CSRF bypass via injected JS\n - Account takeover depending on cookie/session strategy\n\nAffected applications should upgrade to a patched version immediately.",
11+
"severity": [
12+
{
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "npm",
21+
"name": "svelte"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "5.46.0"
29+
},
30+
{
31+
"fixed": "5.46.4"
32+
}
33+
]
34+
}
35+
],
36+
"database_specific": {
37+
"last_known_affected_version_range": "<= 5.46.3"
38+
}
39+
}
40+
],
41+
"references": [
42+
{
43+
"type": "WEB",
44+
"url": "https://github.com/sveltejs/svelte/security/advisories/GHSA-6738-r8g5-qwp3"
45+
},
46+
{
47+
"type": "WEB",
48+
"url": "https://github.com/sveltejs/svelte/commit/ef81048e238844b729942441541d6dcfe6c8ccca"
49+
},
50+
{
51+
"type": "PACKAGE",
52+
"url": "https://github.com/sveltejs/svelte"
53+
},
54+
{
55+
"type": "WEB",
56+
"url": "https://github.com/sveltejs/svelte/releases/tag/svelte%405.46.4"
57+
}
58+
],
59+
"database_specific": {
60+
"cwe_ids": [
61+
"CWE-79"
62+
],
63+
"severity": "MODERATE",
64+
"github_reviewed": true,
65+
"github_reviewed_at": "2026-01-15T20:13:33Z",
66+
"nvd_published_at": null
67+
}
68+
}
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-w54x-r83c-x79q",
4+
"modified": "2026-01-15T20:14:31Z",
5+
"published": "2026-01-15T20:14:31Z",
6+
"aliases": [],
7+
"summary": "Pepr Has Overly Permissive RBAC ClusterRole in Admin Mode",
8+
"details": "Severity: LOW\nTarget: /workspace/pepr/src/lib/assets/rbac.ts\nEndpoint: Kubernetes RBAC configuration\nMethod: Deployment\n\n## Response / Rationale\nPepr defaults to `rbacMode: \"admin\"` because the initial experience is designed to be frictionless for new users. This mode ensures that users can deploy and run the default `hello-pepr.ts` module without needing to understand or pre-configure RBAC rules.\n\nIt’s important to note that `hello-pepr.ts` is intended strictly as a demo to showcase Pepr features and workflow. It is not intended for production use, and the documentation explicitly calls out that admin RBAC should not be used in production environments.\n\nThat said, if a user skips the documentation and does not review the `npx pepr build` options, they could deploy a module with broader privileges than necessary.\n\nWe consider this low severity because Pepr is a framework: the module author is ultimately responsible for selecting the appropriate RBAC scope for their module and environment as each module has different RBAC needs and requirements. \n\nOur security focus is on ensuring the Pepr controller and runtime components operate securely within Kubernetes, while still allowing developers the flexibility to build modules with the access they require.\n\nIn order to fix this we will warn the user in logs that the default `ClusterRole` is `cluster-admin` and that it is not recommended for production.\n\n## How this can be exploited\n\nThis vulnerability can be exploited by doing a build and deploying your Pepr module with cluster-admin role instead of using `npx pepr build --rbac-mode=scoped`.",
9+
"severity": [
10+
{
11+
"type": "CVSS_V4",
12+
"score": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:U"
13+
}
14+
],
15+
"affected": [
16+
{
17+
"package": {
18+
"ecosystem": "npm",
19+
"name": "pepr"
20+
},
21+
"ranges": [
22+
{
23+
"type": "ECOSYSTEM",
24+
"events": [
25+
{
26+
"introduced": "1.0.0"
27+
},
28+
{
29+
"fixed": "1.0.4"
30+
}
31+
]
32+
}
33+
]
34+
}
35+
],
36+
"references": [
37+
{
38+
"type": "WEB",
39+
"url": "https://github.com/defenseunicorns/pepr/security/advisories/GHSA-w54x-r83c-x79q"
40+
},
41+
{
42+
"type": "PACKAGE",
43+
"url": "https://github.com/defenseunicorns/pepr"
44+
},
45+
{
46+
"type": "WEB",
47+
"url": "https://github.com/defenseunicorns/pepr/releases/tag/v1.0.4"
48+
}
49+
],
50+
"database_specific": {
51+
"cwe_ids": [
52+
"CWE-276"
53+
],
54+
"severity": "LOW",
55+
"github_reviewed": true,
56+
"github_reviewed_at": "2026-01-15T20:14:31Z",
57+
"nvd_published_at": null
58+
}
59+
}

0 commit comments

Comments
 (0)