CVE-2026-72861Public exploitNetwork attack vector

Unauthenticated comment posting via skipped signature check

Published Aug 20, 2026 · Updated Aug 20, 2026

Authentication bypass in Appwrite Templates github-issue-bot 1.1.2 and earlier allows remote attackers to post GitHub comments via forged webhooks. In node/github-issue-bot/src/github.js and node-typescript/github-issue-bot/src/github.ts, verifyWebhook returns success when x-hub-signature-256 is absent because the missing-header test is ORed with the HMAC verification call. Reachability is network-based and unauthenticated; once the check is bypassed, main.js passes repository and issue objects from the request body into postComment, allowing attacker-chosen comment targets under the configured GITHUB_TOKEN.

CVSS severity6.9
Medium
EPSS probability0.20%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authentication bypass in Appwrite Templates github-issue-bot 1.1.2 and earlier allows remote attackers to post GitHub comments via forged webhooks. In node/github-issue-bot/src/github.js and node-typescript/github-issue-bot/src/github.ts, verifyWebhook returns success when x-hub-signature-256 is absent because the missing-header test is ORed with the HMAC verification call. Reachability is network-based and unauthenticated; once the check is bypassed, main.js passes repository and issue objects from the request body into postComment, allowing attacker-chosen comment targets under the configured GITHUB_TOKEN.

The record

CVE
CVE-2026-72861
Published
Aug 20, 2026
Updated
Aug 20, 2026
Vendor
Appwrite
Product
Appwrite Templates
Classifications
CWE-347, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=1.1.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Appwrite · Appwrite Templatesversion=0 <=1.1.2

Published CVSS scores

6.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo