CVE-2026-122075: Authorization bypass in Drupal Scheduler publication scheduling
The Drupal Scheduler module insufficiently checks authorization when publication or unpublication dates are modified through a web services API. Users who have permission to edit affected content can change its scheduling dates without the required scheduling authorization. This can expose content before its intended publication time or alter when content becomes inaccessible.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Unauthorized schedule changes can compromise content confidentiality and integrity by publishing information prematurely or changing its intended availability period. Content may become inaccessible earlier or later than planned.
Mitigation
If you can’t patch tonight, do this now.
Pending upgrade, restrict permission to edit affected content and access to web services API editing operations to trusted users. These restrictions reduce exposure but do not correct the authorization flaw.
Remediation
Patch, then assume compromise.
Upgrade Scheduler 8.x-1.x to 8.x-1.7, 2.2.x to 2.2.3, and 2.3.x to 2.3.1. Migrate the unsupported 2.1.x branch to 2.2.3 or 2.3.1. Version 2.0.x is also identified as affected and should be migrated to a supported fixed release. Although the advisory's affected-version expression does not explicitly include 2.3.x, its upgrade instructions specify 2.3.1 for that branch.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-122075 exploited in the wild?
- As of Nov 4, 2026, Mallory has no reports of CVE-2026-122075 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-122075?
- As of Nov 4, 2026, Mallory has found no public exploit for CVE-2026-122075.
- Is there a patch for CVE-2026-122075?
- Upgrade Scheduler 8.x-1.x to 8.x-1.7, 2.2.x to 2.2.3, and 2.3.x to 2.3.1. Migrate the unsupported 2.1.x branch to 2.2.3 or 2.3.1.
Recent activity
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.