{"answers":{"affected":"2 open source packages ship an affected version, including code16/sharp.","exploited":"There is no known exploitation of CVE-2026-53634 in the wild and no public exploit code.","fix":"Upgrade code16/sharp to 9.22.3 or later.","what":"CVE-2026-53634 is a medium-severity missing authorization vulnerability in code16 sharp, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53634 and fix it if it is affected.\n\nWhat it is: CVE-2026-53634 is a medium-severity missing authorization vulnerability in code16 sharp, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53634 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- code16/sharp (Packagist): affected from 9.0.0; fixed in 9.22.3\n- code16/sharp (Packagist): affected from 9.0.0; fixed in 9.22.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-53634/ (Markdown: https://insights.sbomify.com/CVE-2026-53634/index.md)","id":"CVE-2026-53634","markdown":"https://insights.sbomify.com/CVE-2026-53634/index.md","name":"CVE-2026-53634","record":{"aliases":["GHSA-vmwx-m75v-qvch"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel CMS framework","requires_auth":"low_privilege","summary":"Authenticated users can bypass authorization checks to view creation forms or submit records for entities they lack permission to access.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Sharp is a content management framework built for Laravel as a package. From version 9.0.0 to before version 9.22.3, 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. This issue has been patched in version 9.22.3.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Sharp: Missing Authorization Check in Quick Creation Command Endpoints","id":"CVE-2026-53634","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Open edX Platform: Insufficient Permission on set_course_mode_price()","id":"CVE-2026-53635"},"packages":[{"ecosystem":"Packagist","fixed":["9.22.3"],"introduced":["9.0.0"],"last_affected":[],"package":"code16/sharp","purl":null,"source":"GHSA-vmwx-m75v-qvch"},{"ecosystem":"Packagist","fixed":["9.22.3"],"introduced":["9.0.0"],"last_affected":[],"package":"code16/sharp","purl":"pkg:composer/code16/sharp","source":"GHSA-vmwx-m75v-qvch"}],"prev":{"headline":"Vitest: Exposed Browser Mode API Can Proxy CDP and Overwrite Config Files, Leading to RCE","id":"CVE-2026-53633"},"products":["sharp"],"published":"2026-06-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-11","vendors":["code16"]},"summary":"Authenticated users can bypass authorization checks to view creation forms or submit records for entities they lack permission to access.","url":"https://insights.sbomify.com/CVE-2026-53634/"}