CVE-2026-55806: Drupal core - Less critical - Cache poisoning and open redirect - SA-CORE-2026-007
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Drupal Drupal core 10.5.12, 10.6.11, 11.0.*.
Low priority for now. Upgrade to Drupal Drupal core 10.5.12, 10.6.11, 11.0.* or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
URL 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.*.
- Published
- Jul 10, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.3% · 27th percentile
- CWE
- CWE-601
Report tools
Action score
23
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| drupal | drupal | cpe:2.3:a:drupal:drupal |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (drupal). Independent of NVD's CPE analysis and usually ahead of it.
Drupal Drupal core
- 0.0.0 and later · before 10.5.12affected · semver
- 10.6.0 and later · before 10.6.11affected · semver
- 11.2.0 and later · before 11.2.14affected · semver
- 11.3.0 and later · before 11.3.12affected · semver
- 0.0.0 and later · before 11.0.*affected · semver
- 0.0.0 and later · before 11.1.*affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- drupal drupalbefore 10.5.12
- drupal drupal10.6.0 and later · before 10.6.11
- drupal drupal11.0.0 and later · before 11.2.14
- drupal drupal11.3.0 and later · before 11.3.12
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | drupal/core | from 10.6.0 · before 10.6.11 | 10.6.11 |
| Packagist | drupal/core | from 11.0.0 · before 11.1.0 | 11.1.0 |
| Packagist | drupal/core | from 11.1.0 · before 11.2.0 | 11.2.0 |
| Packagist | drupal/core | from 11.2.0 · before 11.2.14 | 11.2.14 |
| Packagist | drupal/core | from 11.3.0 · before 11.3.12 | 11.3.12 |
| Packagist | drupal/core | before 10.5.12 | 10.5.12 |
Same product
drupal: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-7602Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-004KEV99Now
- CVE-2018-7600Drupal before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6, and 8.5.x before 8.5.1 allows remote attackers to execute arbitrary code because…KEV99Now
- CVE-2026-9082Drupal core - Highly critical - SQL injection - SA-CORE-2026-004KEV96Now
Published before and after this one in the same product
- ← EarlierCVE-2026-55803Jul 10, 2026 · Drupal core - Critical - PHP object injection - SA-CORE-2026-00523Monitor
- ← EarlierCVE-2026-55804Jul 10, 2026 · Drupal core - Moderately critical - Gadget chain - SA-CORE-2026-00623Monitor
- Later →CVE-2026-55807Jul 10, 2026 · Drupal core - Moderately critical - Server-side request forgery - SA-CORE-2026-00812Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Drupal Drupal core | 10.5.12 | Vendor (CNA) |
| Drupal Drupal core | 10.6.11 | Vendor (CNA) |
| Drupal Drupal core | 11.0.* | Vendor (CNA) |
| Drupal Drupal core | 11.1.* | Vendor (CNA) |
| Drupal Drupal core | 11.2.14 | Vendor (CNA) |
| Drupal Drupal core | 11.3.12 | Vendor (CNA) |
| Packagist:drupal/core | 10.5.12 | Package registry (OSV) |
| Packagist:drupal/core | 10.6.11 | Package registry (OSV) |
| Packagist:drupal/core | 11.1.0 | Package registry (OSV) |
| Packagist:drupal/core | 11.2.0 | Package registry (OSV) |
| Packagist:drupal/core | 11.2.14 | Package registry (OSV) |
| Packagist:drupal/core | 11.3.12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Dave Long (longwave)coordinator
- Melih Acikozfinder
- Michael Winser (michaelwinser)finder
- James Gilliland (neclimdul)coordinator
- Jess (xjm)coordinator
- catch (catch)coordinator
- cilefen (cilefen)coordinator
- Willem Drupal enthousiast (willempje2)finder
- Greg Knaddison (greggles)coordinator
- Lee Rowlands (larowlan)remediation developer
- Juraj Nemec (poker10)coordinator
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.