VDB
GCVE-110-TWILIO-2026-0022
GCVE-110-TWILIO-2026-0022
Advisory Published
<p>Customers can now use the Consent Management API to programmatically re-opt-in users on US and Canada Toll-Free numbers.</p>
<p>Previously, opt-outs on US/CA Toll free numbers were strictly enforced at the network level, meaning an opt out block could only be lifted if the user texted an opt-in keyword like "START". Now, if a user provides valid re-opt-in consent outside of a messaging channel (e.g., via a web form, email, or in-app preference center), you can log their updated consent directly through the Consent Management API. Twilio will automatically pass this signal to downstream networks to clear the opt-out block and resume messaging.</p>
<p>Key Highlights:</p>
<ul>
<li><p>Programmatic Re-Opt-In: Seamlessly restore message deliverability for users who re-consent via external channels.</p>
</li>
<li><p>Fewer Failed Sends: Eliminate <a href="https://www.twilio.com/docs/api/errors/21610">21610 </a>(Unsubscribed Recipient) and <a href="https://www.twilio.com/docs/api/errors/30004">30004</a> (Message Blocked) error codes for users who have re-consented to receive messages.</p>
</li>
<li><p>Centralized Compliance: Keep your Twilio messaging traffic perfectly synced with your CRM and internal omnichannel engagement and consent workflows.</p>
</li>
</ul>
<p>For more information, see our <a href="https://www.twilio.com/docs/messaging/features/consent-api">Consent Management API docs</a>.</p>
References
Browse GCVE Records
1,895 records in the GCVE database · Updated September 4, 2026
No matching records found.
Explore Further
Investigate this vulnerability in the interactive console or download the raw GCVE record.