Categories
CVE-2026-8495 critical CVSS 9.8

Vulnerability in drupal/date_ical (CVE-2026-8495)

Summary

Vulnerability in drupal/date_ical (CVE-2026-8495). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.0.15 or later.

Original description

The description as published by the source.

Missing Authorization vulnerability in Drupal Date iCal allows Forceful Browsing.

This issue affects Date iCal: from 0.0.0 before 4.0.15.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-8495 has been found in drupal/date_ical.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade drupal/date_ical to 4.0.15 or later.
If unsure, ask your IT team or search "drupal/date_ical CVE-2026-8495" on the vendor's site.

CVE-2026-8495 (drupal/date_ical) — CWE-862 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.0.15 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-862) exists in drupal/date_ical.

📍 Affected scope

Check the vendor advisory for the affected versions of drupal/date_ical.

🔥 Severity

Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 4.0.15.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'drupal/date_ical' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'drupal/date_ical' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で drupal/date_ical を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade drupal/date_ical to 4.0.15

    ステージング環境で 4.0.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Packagist:https://packages.drupal.org/8 drupal/date_ical
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.15"}],"database_specific":{"constraint":"<4.0.15"}}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details