CVE-2026-72861
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 10% of all known CVEs.
References
Related Vulnerabilities
Other CWE-347 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2018-16042 | Medium | 6.5 | 82% | - | - |
| CVE-2025-59718 | Critical | 9.8 | 69% | KEV | Fix |
| CVE-2025-25292 | Critical | 9.8 | 65% | - | Fix |
| CVE-2021-22160 | Critical | 9.8 | 53% | - | Fix |
| CVE-2013-3900 | Medium | 5.5 | 45% | KEV | - |
| CVE-2018-0114 | High | 7.5 | 43% | - | Fix |
Common questions
How do I fix CVE-2026-72861?
No published fix for CVE-2026-72861 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-72861 being actively exploited?
Not that we know of. CVE-2026-72861 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.20% is the estimated probability that it will be exploited in the next 30 days. That is higher than 10% of all scored CVEs.
How severe is CVE-2026-72861?
CVE-2026-72861 has a CVSS v3 base score of 5.8, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-72861
Markdown
[](https://tridentstack.com/cve/CVE-2026-72861)HTML
<a href="https://tridentstack.com/cve/CVE-2026-72861"><img src="https://tridentstack.com/cve/badge/CVE-2026-72861.svg" alt="CVE-2026-72861"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-21.