PatchSiren cyber security CVE debrief
CVE-2026-80207 apitable CVE debrief
CVE-2026-80207 is a medium-severity vulnerability in APITable through 1.13.0-beta.1. An unauthenticated attacker can create arbitrary notifications in apitable_player_notification against any user ID, which are stored with the system sender and rendered in the victim's inbox as legitimate system notifications. This vulnerability allows an attacker to persist notifications with arbitrary content, posing a risk to APITable deployments. The vulnerability is caused by the InternalNotifyController's create handler being annotated with requiredLogin = false, allowing unauthenticated clients to create notifications. The nginx gateway proxies /api requests to the backend server, making the
- Vendor
- apitable
- Product
- Unknown
- CVSS
- MEDIUM 6.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-27
- Original CVE updated
- 2026-09-23
- Advisory published
- 2026-08-27
- Advisory updated
- 2026-09-23
Who should care
Defenders responsible for APITable deployments and security should assess exposure and prioritize remediation due to the medium severity risk of unauthenticated notification creation.
Why it matters
CVE-2026-80207 is a medium-severity vulnerability allowing unauthenticated notification creation in APITable, posing a risk to deployments. Defenders should verify and remediate this vulnerability.
- Unauthenticated creation of arbitrary notifications
- Notifications can be stored with the system sender
- Victims may receive notifications as if from the system
- Verification of APITable version and endpoint authentication is required
Technical summary
The vulnerability is caused by the InternalNotifyController's create handler being annotated with requiredLogin = false, which allows unauthenticated clients to create notifications. The nginx gateway proxies /api requests to the backend server, making the endpoint reachable without authentication. An attacker can persist arbitrary notifications in apitable_player_notification against any user ID they name, and because fromUserId can be set to 0 the message is stored with the system sender and renders in the victim's inbox as a legitimate system notification. The body extras content is stored verbatim and forwarded to the frontend. To exploit this vulnerability, an attacker only needs to be able to reach the
Defensive priority
Defenders should prioritize verifying and remediating this vulnerability, especially those responsible for APITable deployments and security.
Recommended defensive actions
- Verify APITable version and check if the system is vulnerable
- Implement authentication for the internal notification create endpoint
- Monitor for suspicious notification activity
- Apply patches or updates provided by the vendor
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The vulnerability allows unauthenticated creation of notifications due to missing authentication on the internal notification create endpoint. This is supported by the CVE description and source references.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-80207 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-80207
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-80207 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-80207
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/apitable/apitable
-
Source reference
Unverified legacy reference
URL: https://github.com/apitable/apitable/blob/88b24ce9f359cc434778be75d03603182882dc76/backend-server/application/src/main/java/com/apitable/internal/controller/InternalNotifyController.java
-
Source reference
Unverified legacy reference
URL: https://github.com/apitable/apitable/issues/1813
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/apitable-through-1.13.0-beta.1-missing-authentication-on-the-internal-notification-create-endpoint
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.