CVE-2026-107267 drupal CVE debrief

Who should care

Drupal site administrators and security teams should assess exposure and verify DKAN module versions. They should review access controls and update or adjust configurations as necessary to prevent potential access bypass. This includes verifying DKAN module version, reviewing access controls, and updating or adjusting configurations as necessary.

Why it matters

Defenders should care about this vulnerability as it could lead to unauthorized access and data exposure in Drupal sites using the DKAN module. Site administrators and security teams should verify their DKAN module version, review access controls, and update or adjust configurations as necessary to prevent potential access bypass.

• Potential unauthorized access to data via DKAN datastore endpoints.
• Need to verify and adjust access controls for the DKAN module.
• Possible impact on data integrity if access controls are not properly configured.

Technical summary

The DKAN module for Drupal does not correctly check access for all of its endpoints, potentially leading to an access bypass. This issue is mitigated as it only impacts sites that do not give 'access content' permission to the anonymous role. The vulnerability is confirmed in DKAN module versions less than 4.0.4 and 4.1.0 to 4.1.4. Official sources indicate that sites with 'access content' permission granted to the anonymous role are not impacted. Defenders should prioritize verifying their DKAN module version and ensuring proper access controls are in place.

Defensive priority

Defenders should prioritize verifying their DKAN module version and ensuring proper access controls are in place.

Recommended defensive actions

• Verify DKAN module version and update to 4.0.4 or later if using a vulnerable version.
• Ensure 'access content' permission is not granted to the anonymous role if not required.
• Review and adjust access controls for DKAN datastore endpoints.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The vulnerability is confirmed in DKAN module versions less than 4.0.4 and 4.1.0 to 4.1.4. Official sources indicate that sites with 'access content' permission granted to the anonymous role are not impacted.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.