- Exploited
- No known exploitation
- Fix
- Fixed in 1.2.17
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.2.17.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Drupal consent module "drupal/cookies" has a flaw in its COOKiES Video submodule, where the value of the data-cookies-video-blazy-src attribute is not checked properly before being converted into a src attribute for Blazy iframes. An attacker who can get the right permissions and place a specific HTML element with a certain class on the site could inject a malicious source value that displays to all users.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
This module enables you to manage user consent for external services, such as embedded videos. The COOKiES Video submodule blocks external video elements until the visitor accepts the consent banner, then re-enables them.
The module doesn't sufficiently check the value of the data-cookies-video-blazy-src attribute when it converts it back to a src attribute for Blazy iframes. The protocol check added in SA-CONTRIB-2025-092 covered the other conversion paths but missed this one.
This vulnerability is mitigated by the fact that an attacker must have the correct permissions to have a specific HTML element display for all users, and that element must have a specific class set.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects Packagist packages
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.2.17.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by DRUPAL-CONTRIB-2026-334 (This module enables you to manage user consent for external services, such as embedded videos.), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for DRUPAL-CONTRIB-2026-334 (entry last updated 2026-11-11):
Affected:
- Packagist package drupal/cookies: fixed in 1.2.17
Fixed versions: 1.2.17.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: DRUPAL-CONTRIB-2026-334 is not listed as of cve.now's last read.
This KEV status is for DRUPAL-CONTRIB-2026-334 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.drupal.org/sa-contrib-2026-334
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/DRUPAL-CONTRIB-2026-334
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "DRUPAL-CONTRIB-2026-334"}.Timeline
- Advisory published
- Record last updated
- First seen by cve.now
Affected versions
- drupal/cookiesPackagist
fixed in 1.2.17
Evidence 1
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about DRUPAL-CONTRIB-2026-334
Is DRUPAL-CONTRIB-2026-334 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by DRUPAL-CONTRIB-2026-334?
drupal/cookies (Packagist): before 1.2.17.Source: cve.now feed data
How do I fix DRUPAL-CONTRIB-2026-334?
Upgrade to a fixed version: 1.2.17.Source: cve.now feed data