<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>RADAR — GitHub advisories — npm</title>
    <link>https://radar.trulysovereign.com</link>
    <atom:link href="https://radar.trulysovereign.com/feeds/source/github-advisories-npm.xml" rel="self" type="application/rss+xml"/>
    <description>Changes RADAR detected at GitHub advisories — npm.</description>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 19:19:18 GMT</lastBuildDate>
    <item>
      <title>Budibase allows unauthenticated global-admin creation via init guard bypass</title>
      <link>https://radar.trulysovereign.com/items/e2c9fbb6-b972-4a0d-82a9-c86713ba70fa</link>
      <guid isPermaLink="false">e2c9fbb6-b972-4a0d-82a9-c86713ba70fa</guid>
      <pubDate>Sat, 21 Nov 2026 19:18:55 GMT</pubDate>
      <category>verify_exposure</category>
      <source url="https://api.github.com/advisories?ecosystem=npm&amp;severity=high&amp;per_page=100">GitHub advisories — npm</source>
      <description>CVE-2026-122247 published 20 November 2026 documents an unauthenticated vulnerability in @budibase/server that allows creation of global-admin accounts and databases by bypassing the one-time initialization guard on POST /api/global/users/init through tenant confusion. GitHub rates this high severity. No patched version is listed in the advisory.

Why it matters: An unauthenticated attacker can create admin accounts with full privileges, bypassing the intended one-time setup restriction. This grants complete control over the Budibase instance and its databases without any prior access.

What to do: Check whether you run @budibase/server in production. If so, verify whether the /api/global/users/init endpoint is exposed and whether unauthorized admin accounts exist. Remediation: see bulletin https://github.com/advisories/GHSA-25qc-m4pw-2w8r</description>
    </item>
    <item>
      <title>CodeWhale auto_approve defaults to true, bypassing task-path hardening</title>
      <link>https://radar.trulysovereign.com/items/152a381f-f439-4071-acb0-3f82400d19b0</link>
      <guid isPermaLink="false">152a381f-f439-4071-acb0-3f82400d19b0</guid>
      <pubDate>Fri, 20 Nov 2026 07:20:26 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=npm&amp;severity=high&amp;per_page=100">GitHub advisories — npm</source>
      <description>GitHub published GHSA-8hp3-xxrg-v9c8 (CVE-2026-83817) on 19 November 2026, rating it high severity. The advisory states that CodeWhale's automation auto_approve parameter defaults to true, which bypasses the task-path hardening fix intended to prevent silent recurring agent execution. Patched in version 0.9.0 for both codewhale and codewhale-tui packages.

Why it matters: The default configuration allows agents to execute tasks without approval, circumventing security controls designed to prevent unauthorized recurring execution. The triage notes indicate an active abuse pattern involving silent recurring agent execution.

What to do: Upgrade codewhale and codewhale-tui to version 0.9.0. If you cannot upgrade immediately, explicitly set auto_approve to false in automation configurations to restore the intended approval gate.</description>
    </item>
    <item>
      <title>Effect 3.22.1 patches ReDoS in Schema.TemplateLiteral regex</title>
      <link>https://radar.trulysovereign.com/items/0b1127fa-f36c-4e64-b6bc-be7431dc8609</link>
      <guid isPermaLink="false">0b1127fa-f36c-4e64-b6bc-be7431dc8609</guid>
      <pubDate>Fri, 20 Nov 2026 07:20:17 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=npm&amp;severity=high&amp;per_page=100">GitHub advisories — npm</source>
      <description>CVE-2026-121707 discloses a regular expression denial of service vulnerability in the effect npm package's Schema.TemplateLiteral compiled regex. GitHub rated it high severity. Effect 3.22.1 patches the issue, published 19 November 2026.

Why it matters: An attacker who controls input to Schema.TemplateLiteral can cause the regex engine to hang, blocking the event loop and denying service to other requests in the same process.

What to do: Update effect to 3.22.1 or later if you use Schema.TemplateLiteral with untrusted input. Check your dependency tree for transitive uses of effect.</description>
    </item>
    <item>
      <title>CodeWhale TUI exec_shell classifier enables silent RCE via grep flags</title>
      <link>https://radar.trulysovereign.com/items/c5c5abc6-5a16-4cd6-8fbd-beedf7fa6c86</link>
      <guid isPermaLink="false">c5c5abc6-5a16-4cd6-8fbd-beedf7fa6c86</guid>
      <pubDate>Fri, 20 Nov 2026 07:20:08 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=npm&amp;severity=high&amp;per_page=100">GitHub advisories — npm</source>
      <description>GitHub published GHSA-3mgh-93r5-r7jf (CVE-2026-83816) on 19 November 2026. CodeWhale TUI versions before 0.9.0 auto-approve exec flags in fd/rg/git grep commands through the parallel-readonly classifier, enabling remote code execution. Severity: high. Patched in version 0.9.0.

Why it matters: An attacker can execute arbitrary code by injecting malicious flags into grep operations that the classifier incorrectly treats as read-only. The 'silent RCE' designation indicates exploitation leaves minimal traces.

What to do: Upgrade codewhale-tui and codewhale packages to version 0.9.0. Grep your dependency trees for 'codewhale-tui' and 'codewhale' to identify affected installations.</description>
    </item>
    <item>
      <title>OpenID4VP accepts forged X.509 certificates reusing trusted anchor Subject DNs</title>
      <link>https://radar.trulysovereign.com/items/abfdb2ae-5c3e-459f-86b8-81f2b746e237</link>
      <guid isPermaLink="false">abfdb2ae-5c3e-459f-86b8-81f2b746e237</guid>
      <pubDate>Thu, 19 Nov 2026 20:40:35 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=npm&amp;severity=high&amp;per_page=100">GitHub advisories — npm</source>
      <description>CVE-2026-75522 published 19 November 2026 for @openeudi/openid4vp. The library's X.509 chain validation accepts a forged certificate that reuses a trusted anchor's Subject Distinguished Name without verifying the signature. Patched in version 0.8.1.

Why it matters: An attacker can present a certificate that appears to chain to a trusted root by copying its Subject DN, bypassing signature verification. This breaks the trust model for any OpenID4VP credential verification that relies on X.509 certificate chains.

What to do: Update @openeudi/openid4vp to 0.8.1 or later. Verify exposure first if you are unsure whether your application uses this library for credential verification.</description>
    </item>
    <item>
      <title>install-artifact-from-github loads native artifacts without integrity verification</title>
      <link>https://radar.trulysovereign.com/items/4676d530-87a0-4e89-b079-4f4ab5e81184</link>
      <guid isPermaLink="false">4676d530-87a0-4e89-b079-4f4ab5e81184</guid>
      <pubDate>Thu, 19 Nov 2026 07:30:38 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=npm&amp;severity=high&amp;per_page=100">GitHub advisories — npm</source>
      <description>CVE-2026-73864 published 18 November 2026 for install-artifact-from-github. The package loads downloaded native artifacts without verifying integrity. Severity rated high. First patched version is 1.7.0.

Why it matters: An attacker who can intercept or modify the download can substitute malicious native code that executes with the privileges of the build or installation process. No integrity check prevents this.

What to do: Update install-artifact-from-github to 1.7.0 or later. Check package.json and lock files for any version below 1.7.0.</description>
    </item>
    <item>
      <title>Command injection in @augment-vir/node grep() via unsanitized searchPattern</title>
      <link>https://radar.trulysovereign.com/items/3c752202-1632-4b5c-9a75-81fc70ebaa8c</link>
      <guid isPermaLink="false">3c752202-1632-4b5c-9a75-81fc70ebaa8c</guid>
      <pubDate>Wed, 18 Nov 2026 20:36:28 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=npm&amp;severity=high&amp;per_page=100">GitHub advisories — npm</source>
      <description>GitHub published GHSA-xvcc-vqjv-phqh on 18 November 2026, a high-severity command injection vulnerability (CVE-2026-63496) in @augment-vir/node. The grep() function does not sanitize the searchPattern parameter. Version 31.73.5 patches the issue.

Why it matters: An attacker who controls the searchPattern argument can execute arbitrary shell commands on the host. Any code path that passes user input or untrusted data to grep() is exploitable.

What to do: Update @augment-vir/node to 31.73.5 or later. Grep your codebase for imports of @augment-vir/node and calls to grep() to confirm exposure before patching.</description>
    </item>
    <item>
      <title>libp2p gossipsub creates unbounded topics map on distinct subscriptions</title>
      <link>https://radar.trulysovereign.com/items/1edbed37-889c-4563-9745-537704453026</link>
      <guid isPermaLink="false">1edbed37-889c-4563-9745-537704453026</guid>
      <pubDate>Wed, 18 Nov 2026 07:32:26 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=npm&amp;severity=high&amp;per_page=100">GitHub advisories — npm</source>
      <description>CVE-2026-119793 published 17 November 2026 for @libp2p/gossipsub. The default configuration creates a permanent topics-map entry for each distinct subscription with no cap, rated high severity. First patched version is 17.0.0.

Why it matters: An attacker can exhaust memory by sending subscriptions with unique topic names, causing denial of service. The map grows without bound in the default configuration.

What to do: Upgrade @libp2p/gossipsub to 17.0.0 or later. If you cannot upgrade immediately, verify whether your application accepts gossipsub subscriptions from untrusted peers.</description>
    </item>
    <item>
      <title>@libp2p/crypto ASN.1 decoder stalls Node event loop on attacker input</title>
      <link>https://radar.trulysovereign.com/items/5f836177-4bb2-4594-830c-3469f1a2924c</link>
      <guid isPermaLink="false">5f836177-4bb2-4594-830c-3469f1a2924c</guid>
      <pubDate>Wed, 18 Nov 2026 07:32:16 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=npm&amp;severity=high&amp;per_page=100">GitHub advisories — npm</source>
      <description>GitHub published GHSA-rvfr-cqwq-rc4j on 17 November 2026. CVE-2026-110789, rated high severity. The ASN.1 DER decoder in @libp2p/crypto drives an unbounded synchronous loop on attacker-controlled length fields, stalling the Node.js event loop before authentication. Patched in version 5.1.22.

Why it matters: An unauthenticated attacker can freeze the event loop by sending crafted input, denying service to all connections handled by that process. The vulnerability is pre-auth, so no credentials or prior access are required.

What to do: Update @libp2p/crypto to 5.1.22 or later. Check your dependency tree for transitive uses of this package — networking libraries commonly pull it in.</description>
    </item>
    <item>
      <title>code-review-mcp-server command injection patched in 1.5.3</title>
      <link>https://radar.trulysovereign.com/items/4e3060ca-5962-4da9-a601-16f9f5dee17b</link>
      <guid isPermaLink="false">4e3060ca-5962-4da9-a601-16f9f5dee17b</guid>
      <pubDate>Tue, 17 Nov 2026 07:56:51 GMT</pubDate>
      <category>patch_now</category>
      <source url="https://api.github.com/advisories?ecosystem=npm&amp;severity=high&amp;per_page=100">GitHub advisories — npm</source>
      <description>GitHub published GHSA-jq3q-62jc-fqq9 on 16 November 2026, documenting a high-severity command injection vulnerability (CVE-2026-68934) in code-review-mcp-server caused by unsanitized folderPath and baseBranch parameters. Version 1.5.3 patches the issue.

Why it matters: An attacker who controls folderPath or baseBranch input can execute arbitrary commands on the host running the MCP server, compromising the system and any repositories or credentials it accesses.

What to do: Upgrade code-review-mcp-server to 1.5.3 or later. Check package.json and lock files for this dependency in developer tooling and CI pipelines.</description>
    </item>
  </channel>
</rss>
