Publish Advisories

GHSA-389r-rccm-h3h5
GHSA-4j36-39gm-8vq8
GHSA-6f6w-6j58-rq76
GHSA-6px9-j4qr-xfjw
GHSA-73hc-m4hx-79pj
GHSA-9m84-wc28-w895
GHSA-hx52-cv84-jr5v
GHSA-pr34-2v5x-6qjq
GHSA-qffp-2rhf-9h96
GHSA-rhr9-hgcm-x289
GHSA-rw8p-c6hf-q3pg

Author: advisory-database[bot]

advisories/github-reviewed/2026/03/GHSA-389r-rccm-h3h5/GHSA-389r-rccm-h3h5.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-389r-rccm-h3h5",
-  "modified": "2026-03-05T00:16:57Z",
+  "modified": "2026-03-09T15:49:19Z",
   "published": "2026-03-05T00:16:57Z",
   "aliases": [
     "CVE-2026-29780"
@@ -40,6 +40,10 @@
       "type": "WEB",
       "url": "https://github.com/GOVCERT-LU/eml_parser/security/advisories/GHSA-389r-rccm-h3h5"
     },
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-29780"
+    },
     {
       "type": "WEB",
       "url": "https://github.com/GOVCERT-LU/eml_parser/issues/88"
@@ -60,6 +64,6 @@
     "severity": "MODERATE",
     "github_reviewed": true,
     "github_reviewed_at": "2026-03-05T00:16:57Z",
-    "nvd_published_at": null
+    "nvd_published_at": "2026-03-07T16:15:55Z"
   }
 }

advisories/github-reviewed/2026/03/GHSA-4j36-39gm-8vq8/GHSA-4j36-39gm-8vq8.json

@@ -1,9 +1,11 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-4j36-39gm-8vq8",
-  "modified": "2026-03-07T02:39:04Z",
+  "modified": "2026-03-09T15:49:03Z",
   "published": "2026-03-07T02:39:04Z",
-  "aliases": [],
+  "aliases": [
+    "CVE-2026-30921"
+  ],
   "summary": "OneUptime: Synthetic Monitor RCE via exposed Playwright browser object",
   "details": "Summary\n\nOneUptime Synthetic Monitors allow low-privileged project users to submit custom Playwright code that is executed on the `oneuptime-probe` service. In the current implementation, this untrusted code is run inside Node's `vm` and is given live host Playwright objects such as `browser` and `page`.\n\nThis creates a distinct server-side RCE primitive: the attacker does not need the classic `this.constructor.constructor(...)` sandbox escape. Instead, the attacker can directly use the injected Playwright `browser` object to reach `browser.browserType().launch(...)` and spawn an arbitrary executable on the probe host/container.\n\nThis appears to be a separate issue from the previously published `node:vm(GHSA-h343-gg57-2q67)` breakout advisory because the root cause here is exposure of a dangerous host capability object to untrusted code, not prototype-chain access to `process`.\n\n## Details\n\nA normal project member can create or edit monitors and monitor tests:\n\n- https://github.com/OneUptime/oneuptime/blob/8e90f451426b160718bdd1796b68c5ec15318101/Common/Models/DatabaseModels/Monitor.ts#L45-L78\n- https://github.com/OneUptime/oneuptime/blob/8e90f451426b160718bdd1796b68c5ec15318101/Common/Models/DatabaseModels/MonitorTest.ts#L27-L60\n\nThe dashboard exposes a Playwright code editor for Synthetic Monitors and allows the user to queue a test run:\n\n- https://github.com/OneUptime/oneuptime/blob/8e90f451426b160718bdd1796b68c5ec15318101/App/FeatureSet/Dashboard/src/Components/Form/Monitor/MonitorStep.tsx#L861-L918\n- https://github.com/OneUptime/oneuptime/blob/8e90f451426b160718bdd1796b68c5ec15318101/App/FeatureSet/Dashboard/src/Components/Form/Monitor/MonitorTest.tsx#L66-L84\n\nThe probe worker polls queued monitor tests and executes them:\n\n- https://github.com/OneUptime/oneuptime/blob/8e90f451426b160718bdd1796b68c5ec15318101/Probe/Jobs/Monitor/FetchMonitorTest.ts#L55-L85\n\nFor `MonitorType.SyntheticMonitor`, the user-controlled `customCode` is passed into `SyntheticMonitor.execute(...)`:\n\n- https://github.com/OneUptime/oneuptime/blob/8e90f451426b160718bdd1796b68c5ec15318101/Probe/Utils/Monitors/Monitor.ts#L323-L338\n\n`SyntheticMonitor.execute(...)` then runs that code through `VMRunner.runCodeInNodeVM(...)` and injects the live Playwright `browser` and `page` objects into the VM context:\n\n- https://github.com/OneUptime/oneuptime/blob/8e90f451426b160718bdd1796b68c5ec15318101/Probe/Utils/Monitors/MonitorTypes/SyntheticMonitor.ts#L156-L168\n\n`VMRunner.runCodeInNodeVM(...)` creates a Node `vm` context and exposes host objects into it, including the additional context objects:\n\n- https://github.com/OneUptime/oneuptime/blob/8e90f451426b160718bdd1796b68c5ec15318101/Common/Server/Utils/VM/VMRunner.ts#L323-L405\n\nThe proxy wrapper blocks only a small set of property names and still forwards normal method calls with the real host `this` binding. Because of that, untrusted monitor code can still use legitimate Playwright methods on the injected `browser` object.\n\nThat is enough for code execution because Playwright's `Browser` exposes `browserType()`, and `BrowserType.launch()` accepts attacker-controlled process launch options such as `executablePath`, `args`, and `ignoreDefaultArgs`. An attacker can therefore cause the probe to spawn an arbitrary executable. Even if Playwright later errors because the spawned process is not a real browser, the command has already executed.\n\nThis same execution path is also used for normal scheduled monitors, not only one-shot monitor tests:\n\n- https://github.com/OneUptime/oneuptime/blob/8e90f451426b160718bdd1796b68c5ec15318101/Probe/Jobs/Monitor/FetchList.ts#L110-L121\n\nAs a result, the issue can be abused either as a one-shot RCE via `Test Monitor` or as a persistent scheduled RCE by saving a malicious Synthetic Monitor.\n\n### PoC\n\n1. Log in as any user with normal project membership.\n2. Go to `Monitors -> Create New Monitor`.\n3. Select `Synthetic Monitor`.\n4. In `Playwright Code`, paste the following script:\n\n```javascript\n const HostFunction =\n    Object.getOwnPropertyDescriptor(console, \"log\").value.constructor;\n\n  return {\n    data: {\n      node: HostFunction('return process.version')(),\n      cwd: HostFunction('return process.cwd()')(),\n      id: HostFunction(\n        'return process.getBuiltinModule(\"child_process\").execSync(\"id\").toString()'\n      )(),\n    },\n  };\n\n```\n\n5. Select any one browser type, for example `Chromium`.\n6. Select any one screen type, for example `Desktop`.\n7. Set retry count to `0`.\n8. Click `Test Monitor` and choose a probe.\n\nExpected result:\n\n- the monitor execution succeeded and in the `Show More Details` the command output is shown.\n<img width=\"899\" height=\"249\" alt=\"image\" src=\"https://github.com/user-attachments/assets/98ebd26f-431b-438e-9459-7deeebf97b18\" />\n\n\n\n### Impact\n\nThis is a server-side `Remote Code Execution` issue affecting the probe component.\n\nWho is impacted:\n\n- any OneUptime deployment where an attacker can obtain ordinary project membership\n- environments where the probe has access to internal services, secrets, Kubernetes metadata, database credentials, proxy credentials, or other cluster-local trust relationships",
   "severity": [

advisories/github-reviewed/2026/03/GHSA-6f6w-6j58-rq76/GHSA-6f6w-6j58-rq76.json

@@ -1,11 +1,13 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-6f6w-6j58-rq76",
-  "modified": "2026-03-07T02:31:58Z",
+  "modified": "2026-03-09T15:48:53Z",
   "published": "2026-03-07T02:31:58Z",
-  "aliases": [],
+  "aliases": [
+    "CVE-2026-30916"
+  ],
   "summary": "Shescape has possible misidentification of shell due to link chains",
-  "details": "### Impact\n\nThis impacts users of Shescape that configure their `shell` to point to a file on disk that is a link to a link. The precise result of being affected depends on the actual shell used and incorrect shell identified by Shescape.\n\nIn particular, an attacker may be able to bypass escaping for the shell being used. This can result, for example, in exposure of sensitive information, consider the following proof of concept (targeting Shescape v2):\n\n```javascript\nimport fs from \"node:fs\";\nimport { exec } from \"node:child_process\";\n\nimport { Shescape } from \"shescape\";\nimport which from \"which\";\n\n/* 1. Set up */\nconst shell = which.sync(\"bash\");\nconst linkToShell = \"./csh\";\nconst linkToLink = \"./link\";\n\nfs.rmSync(linkToLink, { force: true });\nfs.rmSync(linkToShell, { force: true });\nfs.symlinkSync(shell, linkToShell);\nfs.symlinkSync(linkToShell, linkToLink);\n\n/* 2. Misconfiguration */\nconst execOptions = {\n  shell: linkToLink,\n};\n\nconst shescape = new Shescape({\n  shell: execOptions.shell,\n});\n\n/* 3. Payload */\nconst userInput = \"a=:~\";\n\n/* 4. Attack example */\nexec(\n  `echo Hello ${shescape.escape(userInput)}`,\n  { shell: execOptions.shell },\n  (error, stdout) => {\n    fs.rmSync(linkToLink);\n    fs.rmSync(linkToShell);\n\n    if (error) {\n      console.error(`An error occurred: ${error}`);\n    } else {\n      console.log(stdout);\n      // Output:  \"Hello a=:/home/user\"\n    }\n  },\n);\n```\n\n### Patches\n\nThis problem has been patched in [v2.1.9](https://www.npmjs.com/package/shescape/v/2.1.9) which you can upgrade to now.\n\n### Workarounds\n\nIf upgrading is not an option, either avoid using a shell or make sure the shell path you use is not a link to a link.\n\n### Resources\n\n- Shescape Pull Request [#2388](https://github.com/ericcornelissen/shescape/pull/2388)\n- Shescape Release [v2.1.9](https://github.com/ericcornelissen/shescape/releases/tag/v2.1.9)\n\n### For more information\n\n- Comment on Pull Request [#2388](https://github.com/ericcornelissen/shescape/pull/2388)\n- Open an issue at <https://github.com/ericcornelissen/shescape/issues> (New issue > Question)",
+  "details": "### Impact\n\nThis impacts users of Shescape that configure their `shell` to point to a file on disk that is a link to a link. The precise result of being affected depends on the actual shell used and incorrect shell identified by Shescape.\n\nIn particular, an attacker may be able to bypass escaping for the shell being used. This can result, for example, in exposure of sensitive information, consider the following proof of concept (targeting Shescape v2):\n\n```javascript\nimport fs from \"node:fs\";\nimport { exec } from \"node:child_process\";\n\nimport { Shescape } from \"shescape\";\nimport which from \"which\";\n\n/* 1. Set up */\nconst shell = which.sync(\"bash\");\nconst linkToShell = \"./csh\";\nconst linkToLink = \"./link\";\n\nfs.rmSync(linkToLink, { force: true });\nfs.rmSync(linkToShell, { force: true });\nfs.symlinkSync(shell, linkToShell);\nfs.symlinkSync(linkToShell, linkToLink);\n\n/* 2. Misconfiguration */\nconst execOptions = {\n  shell: linkToLink,\n};\n\nconst shescape = new Shescape({\n  shell: execOptions.shell,\n});\n\n/* 3. Payload */\nconst userInput = \"a=:~\";\n\n/* 4. Attack example */\nexec(\n  `echo Hello ${shescape.escape(userInput)}`,\n  { shell: execOptions.shell },\n  (error, stdout) => {\n    fs.rmSync(linkToLink);\n    fs.rmSync(linkToShell);\n\n    if (error) {\n      console.error(`An error occurred: ${error}`);\n    } else {\n      console.log(stdout);\n      // Output:  \"Hello a=:/home/user\"\n    }\n  },\n);\n```\n\n### Patches\n\nThis problem has been patched in [v2.1.9](https://www.npmjs.com/package/shescape/v/2.1.9) which you can upgrade to now.\n\n### Workarounds\n\nIf upgrading is not an option, either avoid using a shell or make sure the shell path you use is not a link to a link.\n\n### References\n\n- Shescape Pull Request [#2388](https://github.com/ericcornelissen/shescape/pull/2388)\n- Shescape Release [v2.1.9](https://github.com/ericcornelissen/shescape/releases/tag/v2.1.9)\n\n### For more information\n\n- Comment on Pull Request [#2388](https://github.com/ericcornelissen/shescape/pull/2388)\n- Open an issue at <https://github.com/ericcornelissen/shescape/issues> (New issue > Question)",
   "severity": [
     {
       "type": "CVSS_V4",

advisories/github-reviewed/2026/03/GHSA-6px9-j4qr-xfjw/GHSA-6px9-j4qr-xfjw.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-6px9-j4qr-xfjw",
-  "modified": "2026-03-05T00:32:19Z",
+  "modified": "2026-03-09T15:49:37Z",
   "published": "2026-03-05T00:32:19Z",
   "aliases": [
     "CVE-2026-29778"
@@ -40,6 +40,10 @@
       "type": "WEB",
       "url": "https://github.com/pyload/pyload/security/advisories/GHSA-6px9-j4qr-xfjw"
     },
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-29778"
+    },
     {
       "type": "PACKAGE",
       "url": "https://github.com/pyload/pyload"
@@ -52,6 +56,6 @@
     "severity": "HIGH",
     "github_reviewed": true,
     "github_reviewed_at": "2026-03-05T00:32:19Z",
-    "nvd_published_at": null
+    "nvd_published_at": "2026-03-07T16:15:54Z"
   }
 }

advisories/github-reviewed/2026/03/GHSA-73hc-m4hx-79pj/GHSA-73hc-m4hx-79pj.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-73hc-m4hx-79pj",
-  "modified": "2026-03-05T21:42:10Z",
+  "modified": "2026-03-09T15:50:08Z",
   "published": "2026-03-05T21:42:10Z",
   "aliases": [
     "CVE-2026-29787"
@@ -40,6 +40,10 @@
       "type": "WEB",
       "url": "https://github.com/doobidoo/mcp-memory-service/security/advisories/GHSA-73hc-m4hx-79pj"
     },
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-29787"
+    },
     {
       "type": "WEB",
       "url": "https://github.com/doobidoo/mcp-memory-service/commit/18f4323ca92763196aa2922f691dfbeb6bd84e48"
@@ -56,6 +60,6 @@
     "severity": "MODERATE",
     "github_reviewed": true,
     "github_reviewed_at": "2026-03-05T21:42:10Z",
-    "nvd_published_at": null
+    "nvd_published_at": "2026-03-07T16:15:55Z"
   }
 }

advisories/github-reviewed/2026/03/GHSA-9m84-wc28-w895/GHSA-9m84-wc28-w895.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-9m84-wc28-w895",
-  "modified": "2026-03-05T22:05:00Z",
+  "modified": "2026-03-09T15:49:52Z",
   "published": "2026-03-05T00:42:55Z",
   "aliases": [
     "CVE-2026-29784"
@@ -43,6 +43,10 @@
       "type": "WEB",
       "url": "https://github.com/TryGhost/Ghost/security/advisories/GHSA-9m84-wc28-w895"
     },
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-29784"
+    },
     {
       "type": "WEB",
       "url": "https://github.com/TryGhost/Ghost/commit/ec065a774fa125953d2aa644a59cd8990329e0a0"
@@ -59,6 +63,6 @@
     "severity": "HIGH",
     "github_reviewed": true,
     "github_reviewed_at": "2026-03-05T00:42:55Z",
-    "nvd_published_at": null
+    "nvd_published_at": "2026-03-07T16:15:55Z"
   }
 }

advisories/github-reviewed/2026/03/GHSA-hx52-cv84-jr5v/GHSA-hx52-cv84-jr5v.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-hx52-cv84-jr5v",
-  "modified": "2026-03-05T00:26:40Z",
+  "modified": "2026-03-09T15:49:25Z",
   "published": "2026-03-05T00:26:40Z",
   "aliases": [
     "CVE-2026-29781"
@@ -40,6 +40,10 @@
       "type": "WEB",
       "url": "https://github.com/BishopFox/sliver/security/advisories/GHSA-hx52-cv84-jr5v"
     },
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-29781"
+    },
     {
       "type": "PACKAGE",
       "url": "https://github.com/BishopFox/sliver"
@@ -52,6 +56,6 @@
     "severity": "LOW",
     "github_reviewed": true,
     "github_reviewed_at": "2026-03-05T00:26:40Z",
-    "nvd_published_at": null
+    "nvd_published_at": "2026-03-07T16:15:55Z"
   }
 }

advisories/github-reviewed/2026/03/GHSA-pr34-2v5x-6qjq/GHSA-pr34-2v5x-6qjq.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-pr34-2v5x-6qjq",
-  "modified": "2026-03-04T22:47:08Z",
+  "modified": "2026-03-09T15:48:27Z",
   "published": "2026-03-04T22:47:08Z",
   "aliases": [
     "CVE-2026-29191"
@@ -59,6 +59,10 @@
       "type": "WEB",
       "url": "https://github.com/zitadel/zitadel/security/advisories/GHSA-pr34-2v5x-6qjq"
     },
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-29191"
+    },
     {
       "type": "PACKAGE",
       "url": "https://github.com/zitadel/zitadel"
@@ -71,6 +75,6 @@
     "severity": "CRITICAL",
     "github_reviewed": true,
     "github_reviewed_at": "2026-03-04T22:47:08Z",
-    "nvd_published_at": null
+    "nvd_published_at": "2026-03-07T15:15:55Z"
   }
 }

advisories/github-reviewed/2026/03/GHSA-qffp-2rhf-9h96/GHSA-qffp-2rhf-9h96.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-qffp-2rhf-9h96",
-  "modified": "2026-03-05T22:05:04Z",
+  "modified": "2026-03-09T15:49:59Z",
   "published": "2026-03-05T00:52:32Z",
   "aliases": [
     "CVE-2026-29786"
@@ -43,6 +43,10 @@
       "type": "WEB",
       "url": "https://github.com/isaacs/node-tar/security/advisories/GHSA-qffp-2rhf-9h96"
     },
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-29786"
+    },
     {
       "type": "WEB",
       "url": "https://github.com/isaacs/node-tar/commit/7bc755dd85e623c0279e08eb3784909e6d7e4b9f"
@@ -60,6 +64,6 @@
     "severity": "HIGH",
     "github_reviewed": true,
     "github_reviewed_at": "2026-03-05T00:52:32Z",
-    "nvd_published_at": null
+    "nvd_published_at": "2026-03-07T16:15:55Z"
   }
 }

advisories/github-reviewed/2026/03/GHSA-rhr9-hgcm-x289/GHSA-rhr9-hgcm-x289.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-rhr9-hgcm-x289",
-  "modified": "2026-03-04T22:09:11Z",
+  "modified": "2026-03-09T15:49:12Z",
   "published": "2026-03-04T22:09:10Z",
   "aliases": [
     "CVE-2026-29771"
@@ -40,6 +40,10 @@
       "type": "WEB",
       "url": "https://github.com/gravitl/netmaker/security/advisories/GHSA-rhr9-hgcm-x289"
     },
+    {
+      "type": "ADVISORY",
+      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-29771"
+    },
     {
       "type": "PACKAGE",
       "url": "https://github.com/gravitl/netmaker"
@@ -52,6 +56,6 @@
     "severity": "HIGH",
     "github_reviewed": true,
     "github_reviewed_at": "2026-03-04T22:09:10Z",
-    "nvd_published_at": null
+    "nvd_published_at": "2026-03-07T16:15:54Z"
   }
 }