Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-vmwx-m75v-qvch

MEDIUM

GHSA-vmwx-m75v-qvch is a medium-severity (CVSS 4.3) CWE-862 vulnerability in code16/sharp. O3 Security confirms whether GHSA-vmwx-m75v-qvch is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Sharp Missing Authorization Check in Quick Creation Command Endpoints

Also known asCVE-2026-53634
Published
Jul 8, 2026
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected
🐘code16/sharp

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

Impact

The create and store endpoints of the Quick Creation Command feature did not enforce any authorization check. An authenticated Sharp user without create permission on a given entity could bypass the authorization layer and either retrieve the creation form or submit new records for that entity, as long as it had a Quick Creation Command handler configured.

Patches

Yes. The fix is included in version 9.22.3. Users should upgrade to that version or later.

Workarounds

Remove or disable Quick Creation Command handlers (quickCreationCommandHandler()) on any entity list where unauthorized access is a concern, until an upgrade is possible.

Resources

PR #729

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistcode16/sharp9.0.0&&< 9.22.39.22.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code16/sharp. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update code16/sharp to 9.22.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vmwx-m75v-qvch is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-vmwx-m75v-qvch is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vmwx-m75v-qvch. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The create and store endpoints of the Quick Creation Command feature did not enforce any authorization check. An authenticated Sharp user without create permission on a given entity could bypass the authorization layer and either retrieve the creation form or submit new records for that entity, as long as it had a Quick Creation Command handler configured. ### Patches Yes. The fix is included in version 9.22.3. Users should upgrade to that version or later. ### Workarounds Remove or disable Quick Creation Command handlers (quickCreationCommandHandler()) on any entity list where un
O3 Security · Impact-Aware SCA

Is GHSA-vmwx-m75v-qvch in your dependencies?

O3 detects GHSA-vmwx-m75v-qvch across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.