Publish GHSA-w54x-r83c-x79q

Author: advisory-database[bot]

advisories/github-reviewed/2026/01/GHSA-w54x-r83c-x79q/GHSA-w54x-r83c-x79q.json

@@ -1,12 +1,16 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-w54x-r83c-x79q",
-  "modified": "2026-01-15T20:14:31Z",
+  "modified": "2026-01-15T22:55:50Z",
   "published": "2026-01-15T20:14:31Z",
   "aliases": [],
   "summary": "Pepr Has Overly Permissive RBAC ClusterRole in Admin Mode",
-  "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`.",
+  "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 is not an inherently exploitable CVE in the traditional sense. It is being flagged because Pepr defaults to a cluster-admin RBAC configuration and does not explicitly force or enforce least-privilege guidance for module authors.\n\nThe default behavior exists to make the “getting started” experience smooth: new users can experiment with Pepr and create resources dynamically without needing to pre-configure RBAC.\n\nRemediation: scope RBAC appropriately before deploying to production. Running:\n\n```bash\nnpx pepr build --rbac-mode=scoped\n```\n\ngenerates the minimum RBAC required for the controller/informer to watch resources. Any additional permissions must be added based on the specific Kubernetes resources and CRUD operations performed by the module",
   "severity": [
+    {
+      "type": "CVSS_V3",
+      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N"
+    },
     {
       "type": "CVSS_V4",
       "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"
@@ -23,10 +27,10 @@
           "type": "ECOSYSTEM",
           "events": [
             {
-              "introduced": "1.0.0"
+              "introduced": "0"
             },
             {
-              "fixed": "1.0.4"
+              "fixed": "1.0.5"
             }
           ]
         }
@@ -38,13 +42,21 @@
       "type": "WEB",
       "url": "https://github.com/defenseunicorns/pepr/security/advisories/GHSA-w54x-r83c-x79q"
     },
+    {
+      "type": "WEB",
+      "url": "https://github.com/defenseunicorns/pepr/pull/2883"
+    },
+    {
+      "type": "WEB",
+      "url": "https://github.com/defenseunicorns/pepr/commit/d4675a662b8602fcde7e4bf603432f2f133b1fd1"
+    },
     {
       "type": "PACKAGE",
       "url": "https://github.com/defenseunicorns/pepr"
     },
     {
       "type": "WEB",
-      "url": "https://github.com/defenseunicorns/pepr/releases/tag/v1.0.4"
+      "url": "https://github.com/defenseunicorns/pepr/releases/tag/v1.0.5"
     }
   ],
   "database_specific": {