Skip to main content
Mallory
UnratedVulnerability

CVE-2026-122075: Authorization bypass in Drupal Scheduler publication scheduling

Updated 17 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-122075CWE-862

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

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.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.