Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

DRUPAL-CONTRIB-2026-229

CVE-2026-107260

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (drupal/sector 10.4.2, 10.3.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist drupal/sector

    Affected
    < 10.3.3>= 10.4.0, < 10.4.2
    Fixed in
    10.3.3, 10.4.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2026-107260: 0.16% estimated exploitation activity in the next 30 days; percentile 5.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Sector is a distribution targeted towards Drupal site builders and site owners who are looking for a fully configured Drupal project out of the box. A module specific to this distribution doesn't sufficiently sanitize media names, potentially leading to an XSS exploit. This vulnerability is mitigated by the fact that an attacker must have a role with the ability to create or edit a media entity.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record DRUPAL-CONTRIB-2026-229

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-107260

Advisory: DRUPAL-CONTRIB-2026-229
IDs: CVE-2026-107260
Record: https://patchnext.com/advisories/cve-2026-107260 (revision 1, source checked 23 Oct 2026, 22:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: drupal/sector 10.4.2, 10.3.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist drupal/sector: affected < 10.3.3; >= 10.4.0, < 10.4.2; fixed in 10.3.3, 10.4.2

## Suggested inspection (read-only)
- Packagist drupal/sector: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on drupal/sector.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2026-229 (OSV record DRUPAL-CONTRIB-2026-229 lists affected ranges: Packagist drupal/sector >=0 =10.4.0 <10.4.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…