DrupalCMS
CVE-2026-55806
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedURL Redirection to Untrusted Site ('Open Redirect') vulnerability in Drupal Drupal core allows Content Spoofing. This issue affects Drupal core versions: from 0.0.0 to 10.5.12, from 10.6.0 to 10.6.11, from 11.2.0 to 11.2.14, from 11.3.0 to 11.3.12, from 0.0.0 to 11.0.*, from 0.0.0 to 11.1.*.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDrupal core contains an open redirect vulnerability where unsanitized user input in URL parameters allows attackers to craft malicious links that redirect users to arbitrary external websites. Combined with content spoofing capabilities, this enables phishing attacks where victims believe they are visiting a trusted Drupal site.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
DrupalCMS
< 10.5.12>= 10.6.0, < 10.6.11>= 11.0.0, < 11.2.14>= 11.3.0, < 11.3.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Drupal core versionCheck the CHANGELOG.txt file in the Drupal root directory for the version number at the top, or run 'drush status' and look for 'Drupal version', or access /admin/reports/status in the browserAffected if The installed version falls within the affected ranges: < 10.5.12, >= 10.6.0 < 10.6.11, >= 11.0.0 < 11.2.14, or >= 11.3.0 < 11.3.12
-
Identify redirect URL parameters in useSearch Drupal configuration and custom modules for code handling 'destination', 'redirect', or 'url' query parameters that might pass user input to header redirects. Check the sites/default/files directory and any custom modules in modules/custom/ for redirect-related code.Affected if The site uses any module or custom code that takes user-controlled URL parameters and passes them to drupal_goto(), $response->headers->set() for Location, or similar redirect functions without validation.
-
Review redirect validation logicExamine Drupal core and any custom code for redirect destination validation. Look for calls to user_input() or $_GET values being used in redirect destinations without filtering. Check if the code validates that redirects stay within the site or use an allowlist.Affected if Redirect functionality allows arbitrary external URLs without validating they are internal paths or on an explicit allowlist of trusted domains.
-
Check for exposed redirect endpointsTest by attempting a URL like /node?destination=http://example.com or /user/login?destination=http://evil.com to see if the site redirects to the external domain. Use a browser or curl to observe the Location header in the response.Affected if The site redirects to arbitrary external domains specified in URL parameters.
A user is affected if their Drupal core version is in the affected ranges AND the site uses functionality that processes user-supplied URL parameters for redirects without validating they point only to internal paths or an allowlisted domain.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.5.1210.6.1111.2.14
Update Drupal core to versions 10.5.13+, 10.6.12+, 11.2.15+, 11.3.13+, or 11.4.0+ to receive the patch. Implement URL validation to ensure redirects only point to internal relative paths or an explicit allowlist of trusted domains.
Drupal 10.6.11+ or 11.3.12+ (latest stable release recommended)
- 1. Identify your current Drupal core version by running `drush status` or checking the CHANGELOG.txt file in your Drupal root directory.
- 2. Determine which upgrade path applies based on your current version: If running 10.5.x, upgrade to 10.5.12 or later; if running 10.6.x, upgrade to 10.6.11 or later; if running 11.0.x or 11.1.x, upgrade to 11.2.14 or later; if running 11.2.x, upgrade to 11.2.14 or later; if running 11.3.x, upgrade to 11.3.12 or later.
- 3. Create a complete backup of your Drupal site database and files before proceeding.
- 4. Update Drupal core using your preferred method: via Composer (`composer require drupal/core:^10.6.11 --with-all-dependencies` or `^11.3.12`), or by downloading the appropriate tar.gz from drupal.org and following the core update procedure.
- 5. Run database updates after the code is updated: `drush updatedb` or via the web interface at /update.php.
- 6. Clear all caches: `drush cr` or through the admin interface.
- 7. Verify the update was successful and test that the open redirect vulnerability is no longer present.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Drupal
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-55806 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-55806 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data