GHSA-gcj7-r3hg-m7w6
OpenClaw's voice-call Twilio replay dedupe now bound to authenticated webhook identity
GHSA-gcj7-r3hg-m7w6 is a low vulnerability (CVSS 3.7) in openclaw, published March 3, 2026. No source lists public exploit code. Fixed in openclaw 2026.2.26.
- Severity
- 3.7 LowCVSS 3.1, GitHub Advisories
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
2026.2.26openclaw +1 more
Description
Summary
The voice-call Twilio webhook path accepted replay/dedupe identity from unsigned request metadata (i-twilio-idempotency-token), enabling replayed signed requests to bypass replay detection and manager dedupe by mutating only that header.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
<= 2026.2.25(latest published npm version at triage time) - Fixed on
main: commit1aadf26f9acc399affabd859937a09468a9c5cb4 - Planned patched npm version:
2026.2.26
Impact
Deployments using the optional voice-call Twilio webhook path could accept replayed webhook events as fresh events when an attacker had one valid signed request and changed only the unsigned idempotency header.
Technical Details
The fix removes unsigned-header trust from Twilio replay/dedupe identity and binds replay/manager dedupe to authenticated request material. It also threads a verified request identity through provider parsing so dedupe uses verification-derived identity rather than mutable headers.
Fix Commit(s)
1aadf26f9acc399affabd859937a09468a9c5cb4
Release Process Note
patched_versions is pre-set to the planned next release (2026.2.26). After the npm release is published, this advisory can be published without additional version-field edits.
OpenClaw thanks @tdjackey for reporting.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
Affected packages
What each source reports
GitHub Advisories Score used
OpenClaw's voice-call Twilio replay dedupe now bound to authenticated webhook identity
Summary
The voice-call Twilio webhook path accepted replay/dedupe identity from unsigned request metadata (i-twilio-idempotency-token), enabling replayed signed requests to bypass replay detection and manager dedupe by mutating only that header.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
<= 2026.2.25(latest published npm version at triage time) - Fixed on
main: commit1aadf26f9acc399affabd859937a09468a9c5cb4 - Planned patched npm version:
2026.2.26
Impact
Deployments using the optional voice-call Twilio webhook path could accept replayed webhook events as fresh events when an attacker had one valid signed request and changed only the unsigned idempotency header.
Technical Details
The fix removes unsigned-header trust from Twilio replay/dedupe identity and binds replay/manager dedupe to authenticated request material. It also threads a verified request identity through provider parsing so dedupe uses verification-derived identity rather than mutable headers.
Fix Commit(s)
1aadf26f9acc399affabd859937a09468a9c5cb4
Release Process Note
patched_versions is pre-set to the planned next release (2026.2.26). After the npm release is published, this advisory can be published without additional version-field edits.
OpenClaw thanks @tdjackey for reporting.
- Record
GHSA-gcj7-r3hg-m7w6- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L - Weakness
- CWE-294, CWE-345
- Updated
- 2026-11-02
OSV
OpenClaw's voice-call Twilio replay dedupe now bound to authenticated webhook identity
Summary
The voice-call Twilio webhook path accepted replay/dedupe identity from unsigned request metadata (i-twilio-idempotency-token), enabling replayed signed requests to bypass replay detection and manager dedupe by mutating only that header.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
<= 2026.2.25(latest published npm version at triage time) - Fixed on
main: commit1aadf26f9acc399affabd859937a09468a9c5cb4 - Planned patched npm version:
2026.2.26
Impact
Deployments using the optional voice-call Twilio webhook path could accept replayed webhook events as fresh events when an attacker had one valid signed request and changed only the unsigned idempotency header.
Technical Details
The fix removes unsigned-header trust from Twilio replay/dedupe identity and binds replay/manager dedupe to authenticated request material. It also threads a verified request identity through provider parsing so dedupe uses verification-derived identity rather than mutable headers.
Fix Commit(s)
1aadf26f9acc399affabd859937a09468a9c5cb4
Release Process Note
patched_versions is pre-set to the planned next release (2026.2.26). After the npm release is published, this advisory can be published without additional version-field edits.
OpenClaw thanks @tdjackey for reporting.
- Record
GHSA-gcj7-r3hg-m7w6- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L - Weakness
- CWE-294, CWE-345
- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.