Owl Carousel 2 - Critical - Unsupported - SA-CONTRIB-2025-104

published 2025-08-27 last yr. modified 2026-10-08 last mo. also DRUPAL-CONTRIB-2025-104 , EUVD-2025-33785

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 16%
public exploits: 0; none known

Vulnerability in Drupal Owl Carousel 2.This issue affects Owl Carousel 2: *.*.

Is CVE-2025-9554 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: last yr. (2025-10-15)

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	drupal/owlcarousel2	all versions	no fix listed

Affected products

Drupal Owl Carousel 2

References

drupal.org /sa-contrib-2025-104
vendor-advisory, web

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.