OpenClaw's Nextcloud Talk webhook missing rate limiting on shared secret authentication

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2026-33580: 0.37% estimated exploitation activity in the next 30 days; percentile 31.09 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Nextcloud Talk webhook signature failures were not throttled even though the integration relies on an operator-configured shared secret that may be weak. Impact An attacker who could reach the webhook endpoint could brute-force weak secrets online and then forge inbound webhook events. Affected Component extensions/nextcloud-talk/src/monitor.ts Fixed Versions - Affected: <= 2026.3.24 - Patched: = 2026.3.28 - Latest stable 2026.3.28 contains the fix. Fix Fixed by commit e403decb6e (nextcloud-talk: throttle repeated webhook auth failures). OpenClaw thanks @AntAISecurityLab for reporting.

Published by the source

31 Mar 2026, 23:59 UTC

Last modified by the source

6 Apr 2026, 23:12 UTC

Source last checked

26 Oct 2026, 12:47 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9528-x887-j2fp

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9528-x887-j2fp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33580

Advisory: OpenClaw's Nextcloud Talk webhook missing rate limiting on shared secret authentication
IDs: CVE-2026-33580, GHSA-9528-x887-j2fp
Record: https://patchnext.com/advisories/cve-2026-33580 (revision 2, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.3.28. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm openclaw: affected <= 2026.3.24; fixed in 2026.3.28

## Suggested inspection (read-only)
- `npm ls openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openclaw.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9528-x887-j2fp (OSV record GHSA-9528-x887-j2fp lists affected ranges: npm openclaw >=0 <2026.3.28 (fixed))
- Verified: https://github.com/advisories/GHSA-9528-x887-j2fp (GitHub-reviewed advisory GHSA-9528-x887-j2fp lists affected ranges: npm openclaw >=0 <=2026.3.24)

Commands are suggestions: review each one before running it.