CVE-2026-72861: appwrite templates · Improper Verification of Cryptographic Signature
Affects appwrite templatesSource CVE Database V5
Not known to be exploited · CVSS 5.8 Medium.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| appwritetemplates | Affected
| Fixed in– |
GitHubtemplatespkg:github/templatesOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, users should avoid deploying or using the vulnerable github-issue-bot templates or implement additional verification controls to ensure webhook authenticity.
Description
The github-issue-bot templates in appwrite/templates verify the GitHub webhook signature with an inverted condition. verifyWebhook in node/github-issue-bot/src/github.js and in node-typescript/github-issue-bot/src/github.ts returns "typeof signature !== 'string' || (await verify(...))", so when the X-Hub-Signature-256 header is absent the first operand is true, the logical OR short-circuits, and the function reports success without performing any HMAC verification. main.js rejects a request only when verifyWebhook returns false, so an unauthenticated request carrying no signature passes the check. Processing then continues to postComment, which takes the repository and issue objects directly from the request body, letting the caller direct the deployed function to post a comment on a repository and issue of their choosing using the configured GITHUB_TOKEN, with the issue author login from the body interpolated into the comment text.
References
- github.com/appwrite/templates/issues/350 (opens in a new tab)
- github.com/appwrite/templates/blob/1.1.2/node/github-issue-bot/src/github.js (opens in a new tab)
- github.com/appwrite/templates/blob/1.1.2/node-typescript/github-issue-bot/src/github.ts (opens in a new tab)
- github.com/appwrite/templates/blob/1.1.2/node/github-issue-bot/src/main.js (opens in a new tab)
- github.com/appwrite/templates (opens in a new tab)
- vulncheck.com/advisories/appwrite-templates-github-issue-bot-skips-webhook-signature-verification-when-the-x-hub-signature-256-header-is-absent (opens in a new tab)