code16/sharp: Arbitrary class instantiation through the embed_key API parameter

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact An authenticated attacker can instantiate any class in the PHP application by using the embedkey parameter across multiple API endpoints. The instantiation is performed by the Laravel container. As a result, the construct() method of the class is called and all constructor dependencies are resolved. The attacker cannot specify parameter values and cannot call any arbitrary method. Patches The problem has been patched in 9.23.0 and pre-release version 10.0.0-beta.4. An additional check was added to verify that embedkey is a class extending SharpFormEditorEmbed before any instantiation. Workarounds No known workarounds.

Published by the source

12 Nov 2026, 18:18 UTC

Last modified by the source

12 Nov 2026, 18:18 UTC

Source last checked

12 Nov 2026, 18:20 UTC

1. Revision 1 · created · 12 Nov 2026

   Published from ghsa record GHSA-h24v-f482-8cwf

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

# Patch Next advisory brief: CVE-2026-84974

Advisory: code16/sharp: Arbitrary class instantiation through the embed_key API parameter
IDs: CVE-2026-84974, GHSA-h24v-f482-8cwf
Record: https://patchnext.com/advisories/cve-2026-84974 (revision 1, source checked 12 Nov 2026, 18:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: code16/sharp 10.0.0-beta.4, 9.23.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist code16/sharp: affected < 9.23.0; >= 10.0.0-beta.1, < 10.0.0-beta.4; fixed in 9.23.0, 10.0.0-beta.4

## Suggested inspection (read-only)
- Packagist code16/sharp: 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 code16/sharp.
- 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://github.com/advisories/GHSA-h24v-f482-8cwf (GitHub-reviewed advisory GHSA-h24v-f482-8cwf lists affected ranges: Packagist code16/sharp >=0 =10.0.0-beta.1 <10.0.0-beta.4)

Commands are suggestions: review each one before running it.