Quick answers
- Is CVE-2026-53634 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53634 being exploited in the wild.
- How severe is CVE-2026-53634?
- Medium severity, with a CVSS score of 4.3, published 10 June 2026.
- Which products and versions are affected?
- code16/sharp (Packagist) >= 9.0.0, < 9.22.3, ECOSYSTEM:introduced=9.0.0,fixed=9.22.3.
- Is there a fix for CVE-2026-53634?
- Yes. code16/sharp (Packagist): upgrade to 9.22.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53634 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53634?
- Check whether you run code16/sharp (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- code16/sharp (Packagist): upgrade to 9.22.3 or later
composer require code16/sharp:^9.22.3
Technical details
A missing authorization check (CWE-862) exists in the 'create' and 'store' endpoints of the Quick Creation Command feature in code16/sharp. Authenticated users who lack explicit 'create' permissions for a specific entity can bypass the authorization layer if a Quick Creation Command handler is configured for that entity. This allows the attacker to retrieve the creation form or successfully submit new records. The vulnerability is reachable over the network by any authenticated user. A fix is available in version 9.22.3.
Affected products
- code16 sharp >= 9.0.0, < 9.22.3
Identifiers
- CVE-2026-53634
- GHSA-vmwx-m75v-qvch
Timeline
- 2026-06-01: disclosed
- 2026-06-10: advisory: NVD publication date
- 2026-07-08: patched: GitHub Advisory published/updated with patch info