dbcve.org
Date IcalDrupal extension · Date Ical Project

CVE-2026-8495

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 4.0.15 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in Drupal Date iCal allows Forceful Browsing. This issue affects Date iCal: from 0.0.0 before 4.0.15.

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 · moderate confidence

Missing authorization in Drupal's Date iCal module allows forceful browsing, enabling unauthenticated attackers to access calendar resources or pages they should not have permission to view. The vulnerability stems from insufficient access control checks in the module before version 4.0.15.

MitigationUpgrade Date iCal module to version 4.0.15 or later to implement proper authorization checks. If immediate upgrade is not possible, restrict access to the module's URLs at the web server or proxy level.

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
Date IcalDrupal extension
Affected:< 4.0.15

CVSS 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Date iCal module is installed
    Run 'drush pm-list --status=enabled' or check your Drupal modules directory for the date_ical module folder
    Affected if The Date iCal module appears in the enabled module list
  2. Identify the installed Date iCal version
    Run 'drush pm:date_ical' or check the module's info.yml file (usually at modules/date_ical/date_ical.info.yml) for the 'version' field
    Affected if The version number is below 4.0.15 (e.g., 4.0.14, 4.0.13, or any 3.x version)
  3. Verify calendar feed access controls
    Navigate to a calendar feed URL (e.g., /ical/<feeds>) while logged out from an incognito browser and attempt to access it
    Affected if The feed returns calendar data without requiring login or authentication (you can view the iCal content without being logged in)
  4. Check feed permission settings
    In Drupal admin, go to Structure > Feeds (or check the specific feed type configuration) and review the 'Permission' settings under the feed type settings
    Affected if The feed is set to allow 'anonymous user' access or has no role restrictions configured

You are affected if the Date iCal module version is below 4.0.15 AND calendar feeds are accessible without authentication to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.0.15 or later
Fixed in 4.0.15
Interim mitigation

Upgrade Date iCal module to version 4.0.15 or later to implement proper authorization checks. If immediate upgrade is not possible, restrict access to the module's URLs at the web server or proxy level.

Recommended fix High confidence

4.0.15

  1. Backup your Drupal site database and files before making any changes
  2. Run composer update to upgrade the date_ical module: composer require drupal/date_ical:^4.0.15
  3. After the update completes, run database updates: drush updb (or via the administrative UI at /update.php)
  4. Clear the Drupal cache: drush cr (or via the administrative UI at /admin/config/development/performance)
  5. Verify the module is now at version 4.0.15 or later by checking /admin/reports/status or the module's info
Caveat Review the module's release notes for any configuration or functionality changes that may require adjustments to your calendar feeds

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Date Ical Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8495 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8495 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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