How severe is GHSA-8849-cv9f-vccm?

No CVSS score has been assigned to GHSA-8849-cv9f-vccm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8849-cv9f-vccm?

GHSA-8849-cv9f-vccm affects the following packages: drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-8849-cv9f-vccm?

Update drupal/core to 10.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8849-cv9f-vccm is resolved across your whole dependency graph.

How do I detect GHSA-8849-cv9f-vccm in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8849-cv9f-vccm if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-8849-cv9f-vccm actively exploited in the wild?

No public exploit code has been indexed for GHSA-8849-cv9f-vccm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-8849-cv9f-vccm?

GHSA-8849-cv9f-vccm has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 46th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-8849-cv9f-vccm?

GHSA-8849-cv9f-vccm is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8849-cv9f-vccm published, and has it been updated?

GHSA-8849-cv9f-vccm was published on April 26, 2023 and was last updated on December 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Access bypass in Drupal core

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-8849-cv9f-vccm.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

The file download facility doesn't sufficiently sanitize file paths in certain situations. This may result in users gaining access to private files that they should not have access to. Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing private files after updating.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 10.0.0&&< 10.0.8	10.0.8`composer require drupal/core:^10.0.8`
🐘Packagist	`drupal/core`	≥ 9.5.0&&< 9.5.8	9.5.8`composer require drupal/core:^9.5.8`
🐘Packagist	`drupal/core`	≥ 9.0.0&&< 9.4.14	9.4.14`composer require drupal/core:^9.4.14`
🐘Packagist	`drupal/core`	≥ 7.0.0&&< 7.96	7.96`composer require drupal/core:^7.96`

Affected Products

1 product · 4 configurations

Application

drupaldrupal

≥ 10.0 && < 10.0.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/core to 10.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8849-cv9f-vccm is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

The file download facility doesn't sufficiently sanitize file paths in certain situations. This may result in users gaining access to private files that they should not have access to. Some sites may require configuration changes following this security release. Review the release notes for your Drupal version if you have issues accessing private files after updating.

O3 Security · Impact-Aware SCA

Is GHSA-8849-cv9f-vccm in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Access bypass in Drupal coreGHSA-8849-cv9f-vccm