How severe is GHSA-p46m-g734-vpc4?

GHSA-p46m-g734-vpc4 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-p46m-g734-vpc4?

GHSA-p46m-g734-vpc4 affects the following packages: cakephp/debug_kit (Packagist), cakephp/debug_kit (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-p46m-g734-vpc4?

Update cakephp/debug_kit to 4.10.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p46m-g734-vpc4 is resolved across your whole dependency graph.

How do I detect GHSA-p46m-g734-vpc4 in my Packagist dependencies?

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

How do I mitigate GHSA-p46m-g734-vpc4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-p46m-g734-vpc4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p46m-g734-vpc4 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-p46m-g734-vpc4?

GHSA-p46m-g734-vpc4 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th 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-p46m-g734-vpc4?

GHSA-p46m-g734-vpc4 is classified as CWE-470 (CWE-470). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-p46m-g734-vpc4 published, and has it been updated?

GHSA-p46m-g734-vpc4 was published on August 26, 2026 and was last updated on August 26, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

cakephp/debug_kit: MailPreview contains unsafe reflectionGHSA-p46m-g734-vpc4

MEDIUMFix: cakephp/debug_kit#1078

GHSA-p46m-g734-vpc4 is a medium-severity (CVSS 4.3) CWE-470 vulnerability in cakephp/debug_kit. A fix is available for cakephp/debug_kit — see the affected versions and patch details below.

Also known asCVE-2026-54614

Published

Aug 26, 2026

Updated

Aug 26, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-p46m-g734-vpc4.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-p46m-g734-vpc4 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

🐘cakephp/debug_kit🐘cakephp/debug_kit

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

DebugKit provides a debugging toolbar for CakePHP applications. Prior to 4.10.3 and 5.2.4, the DebugKit MailPreview feature in src/Controller/MailPreviewController.php accepts a route-controlled previewName value in findPreview and passes the resolved class from App::className() to constructor execution without rejecting namespace separators or verifying that the class extends DebugKit\Mailer\MailPreview. An attacker able to access DebugKit while debug mode is enabled and the request hostname is local or allowlisted can select an unintended application class through the mail-preview preview route, resulting in arbitrary constructor execution and limited disclosure of application information. This issue is fixed in versions 4.10.3 and 5.2.4.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`cakephp/debug_kit`	all versions	4.10.3`composer require cakephp/debug_kit:^4.10.3`
🐘Packagist	`cakephp/debug_kit`	≥ 5.0.0&&< 5.2.4	5.2.4`composer require cakephp/debug_kit:^5.2.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cakephp/debug_kit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cakephp/debug_kit to 4.10.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p46m-g734-vpc4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact The `MailPreview` feature of debugkit is vulnerable to arbitrary constructor execution. For an application to be vulnerable the following conditions must be true: 1. `debug` mode must be enabled. 2. The hostname must match a 'local' domain or be in an allowlist. ### Patches 5.2.4 and 4.10.3 contain patches for this issue. ### Workarounds Ensure that debugkit is only part of your development dependencies, and that debug mode is disabled in production environments.