CVE-2026-55807: Drupal Core Media Module oEmbed URL Discovery Vulnerability

drupal/core Updated 17 Jun 2026

Summary

17/06/2026
Yes i
Unrated
Not published

CVE-2026-55807: The Media module comes with support for oEmbed. Affects drupal/core across 6 version ranges.

< 10.5.12 >= 10.6.0, < 10.6.11 >= 11.0.0, < 11.1.0 >= 11.1.0, < 11.2.0 >= 11.2.0, < 11.2.14 >= 11.3.0, < 11.3.12

Fixed in 6 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Also tracked for

The same CVE-2026-55807 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Drupal is a popular open-source content management system (CMS) that allows users to create and manage websites. The Media module in Drupal provides support for embedding external content through oEmbed, a format that allows for easy integration of media from various providers. This functionality enhances user experience by allowing seamless media integration. However, the oEmbed specification includes mechanisms for URL discovery, which can be exploited if not properly secured.

Vulnerability Detail

The vulnerability arises from the URL discovery feature of the oEmbed implementation in the Media module of Drupal. This feature can be manipulated to trick Drupal into making unauthorized server-side requests to arbitrary URLs. Such exploitation could lead to various security issues, including data leakage, server-side request forgery (SSRF), and potential access to sensitive information. The vulnerability affects multiple versions of Drupal core, making it critical for users to address it promptly.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 10.5.12 10.5.12
    composer require drupal/core:10.5.12
  • >= 10.6.0, < 10.6.11 10.6.11
    composer require drupal/core:10.6.11
  • >= 11.0.0, < 11.1.0 11.1.0
    composer require drupal/core:11.1.0
  • >= 11.1.0, < 11.2.0 11.2.0
    composer require drupal/core:11.2.0
  • >= 11.2.0, < 11.2.14 11.2.14
    composer require drupal/core:11.2.14
  • >= 11.3.0, < 11.3.12 11.3.12
    composer require drupal/core:11.3.12

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

If you cannot update immediately, consider disabling the Media module or restricting access to the oEmbed functionality until a patch can be applied. This can be done by navigating to the module settings in your Drupal admin interface and disabling the Media module temporarily.

Conclusion

The CVE-2026-55807 vulnerability in the Drupal Core Media module poses significant risks due to its exploitation potential through the oEmbed URL discovery feature. It is crucial for users to update their installations to the latest patched versions to mitigate these risks. Regular monitoring and updates are essential for maintaining the security of your Drupal applications.

See every vulnerability recorded for drupal/core →

Share this vulnerability

FAQ

CVE-2026-55807 is a vulnerability in the Drupal Core Media module that allows unauthorized server-side requests through the oEmbed URL discovery feature.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

The affected versions include Drupal core versions earlier than 10.5.12, between 10.6.0 and 10.6.11, between 11.2.0 and 11.2.14, and between 11.3.0 and 11.3.12, as well as all 11.0.* and 11.1.* versions.

Exploitation of this vulnerability can lead to server-side request forgery (SSRF), data leakage, and unauthorized access to sensitive information on the server.

To apply the patch, update your Drupal core to the latest patched version using Composer. For example, run 'composer update drupal/core' to ensure you have the latest security updates.

Related vulnerabilities

Recent vulnerabilities recorded for drupal/core.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 10.5.12 10.5.12
    composer require drupal/core:10.5.12
  • >= 10.6.0, < 10.6.11 10.6.11
    composer require drupal/core:10.6.11
  • >= 11.0.0, < 11.1.0 11.1.0
    composer require drupal/core:11.1.0
  • >= 11.1.0, < 11.2.0 11.2.0
    composer require drupal/core:11.2.0
  • >= 11.2.0, < 11.2.14 11.2.14
    composer require drupal/core:11.2.14
  • >= 11.3.0, < 11.3.12 11.3.12
    composer require drupal/core:11.3.12

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback