CVE-2026-47212: Symfony Twilio Notifier signature verification bypass in TwilioRequestParser

CVE-2026-47212 · Severity: medium · CVSS 4 · Published 2026-07-14

A vulnerability exists in the Symfony framework's Twilio integration, which is used to process automated notifications from the Twilio communication service. The software fails to verify the digital signature of incoming messages, allowing unauthorized outsiders to send fake status updates or event data to the application. This could lead to incorrect business logic execution or the injection of fraudulent data into the system's records.

Technologies: symfony/symfony (Packagist). Vendors: Packagist, Symfony.

Quick answers

Is CVE-2026-47212 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-47212 being exploited in the wild.
How severe is CVE-2026-47212?
Medium severity, with a CVSS score of 4, published 14 July 2026.
Which products and versions are affected?
symfony/symfony (Packagist) ECOSYSTEM:introduced=6.4.0,fixed=6.4.40; symfony/twilio-notifier (Packagist) ECOSYSTEM:introduced=6.4.0,fixed=6.4.40.
Is there a fix for CVE-2026-47212?
Yes. symfony/symfony (Packagist): upgrade to 6.4.40 or later; symfony/twilio-notifier (Packagist): upgrade to 6.4.40 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47212 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-47212?
Check whether you run symfony/symfony (Packagist), symfony/twilio-notifier (Packagist) or Symfony Twilio Notifier at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • symfony/symfony (Packagist): upgrade to 6.4.40 or later
    composer require symfony/symfony:^6.4.40
  • symfony/twilio-notifier (Packagist): upgrade to 6.4.40 or later
    composer require symfony/twilio-notifier:^6.4.40

Technical details

The vulnerability is classified as Missing Authentication for Critical Function (CWE-306) and Improper Verification of Cryptographic Signature (CWE-347). In affected versions of the Symfony Twilio Notifier component, the `TwilioRequestParser::doParse()` method receives the configured webhook secret but fails to validate the `X-Twilio-Signature` HMAC header against the request payload. An unauthenticated remote attacker can exploit this by sending crafted HTTP POST requests to the webhook endpoint, successfully injecting forged event data. The issue is resolved in Symfony versions 6.4.40, 7.4.12, and 8.0.12 by ensuring the HMAC signature is correctly verified.

Affected products

  • Symfony symfony/symfony >= 6.4.0, < 6.4.40; >= 7.0.0-BETA1, < 7.4.12; >= 8.0.0-BETA1, < 8.0.12
  • Symfony twilio-notifier >= 6.4.0, < 6.4.40; >= 7.0.0-BETA1, < 7.4.12; >= 8.0.0-BETA1, < 8.0.12

Identifiers

  • CVE-2026-47212
  • GHSA-55rj-x2vc-4whq

Timeline

  • 2026-07-14: advisory: NVD and GitHub Security Advisory published
  • 2026-05-20: patched: Fixes released in versions 6.4.40, 7.4.12, and 8.0.12

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.