How severe is CVE-2026-18259?

CVE-2026-18259 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-18259 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-18259?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-18259 published?

CVE-2026-18259 was published on 2026-08-25 and last updated on 2026-08-28.

CVE-2026-18259

CVE-2026-18259 is a high-severity vulnerability with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-208.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (14th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-208
Published: 2026-08-25
Last modified: 2026-08-28

Description

Observable Timing Discrepancy vulnerability in Drupal Token Content Access allows Brute Force. This issue affects Token Content Access versions: from 0.0.0 to 3.1.2.

Frequently asked questions

What is CVE-2026-18259?: Observable Timing Discrepancy vulnerability in Drupal Token Content Access allows Brute Force. This issue affects Token Content Access versions: from 0.0.0 to 3.1.2.
How severe is CVE-2026-18259?: CVE-2026-18259 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-18259 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-18259?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-18259 published?: CVE-2026-18259 was published on 2026-08-25 and last updated on 2026-08-28.

References

https://www.drupal.org/sa-contrib-2026-090

Other CWE-208 vulnerabilities

CVE-2026-77987 — Critical (CVSS 9.8): A server-side request forgery (SSRF) vulnerability was identified in the notebook viewer of GitHub Enterprise Server.…
CVE-2023-41313 — Critical (CVSS 9.8): The authentication method in Apache Doris versions before 2.0.0 was vulnerable to timing attacks. Users are recommended…
CVE-2026-63132 — Critical (CVSS 9.2): OpenBao is an open source identity-based secrets management system. Prior to 2.6.0, OpenBao's handleLogicalRecovery…
CVE-2026-16315 — High (CVSS 8.7): OMICRON StationGuard before version 4.10 contains a cryptographic timing side-channel vulnerability in the backend…
CVE-2024-42512 — High (CVSS 8.6): Vulnerability in the OPC UA .NET Standard Stack before 1.5.374.158 allows an unauthorized attacker to bypass…
CVE-2026-43606 — High (CVSS 8.5): Observable Timing Discrepancy in the AMD Vitis Libraries ECDSA secp256k1 component could allow attackers with local…

Browse all CWE-208 vulnerabilities →