Vulnerability in code16/sharp (CVE-2026-44692)
Summary
Vulnerability in code16/sharp (CVE-2026-44692). Confidential information can be exposed externally. Exploitable via GET /sharp/{globalFilter}/download/{entityKey}/{instanceId. Mitigation: upgrade to 9.22.0 or later.
Original description
The description as published by the source.
Sharp is a content management framework built for Laravel as a package. Prior to version 9.22.0, Sharp exposes a generic download endpoint that authorizes access only to the supplied Sharp entity instance, but then reads the target storage disk and path from request parameters. Because the requested storage object is not bound to the authorized entity instance, an authenticated Sharp user who can view one valid record may use that record as an authorization anchor to download unrelated disk-relative objects from configured Laravel Storage disks. The confirmed impact is authenticated disclosure of unrelated objects from configured Laravel Storage disks. This issue does not imply arbitrary host filesystem access outside configured Laravel Storage disk roots. This issue has been patched in version 9.22.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44692 has been found in code16/sharp.
Attackers can target a specific entry point like GET /sharp/{globalFilter}/download/{entityKey}/{instanceId over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade code16/sharp to 9.22.0 or later.
If unsure, ask your IT team or search "code16/sharp CVE-2026-44692" on the vendor's site.
CVE-2026-44692 (code16/sharp) — CWE-639 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /sharp/{globalFilter}/download/{entityKey}/{instanceId / disk / path / entityKey
Patched: 9.22.0 — apply immediately
Workaround: applications should restrict `downloads.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in code16/sharp. Attackers reach the vulnerable code path via GET /sharp/{globalFilter}/download/{entityKey}/{instanceId.
Check the vendor advisory for the affected versions of code16/sharp. Attack surface: GET /sharp/{globalFilter}/download/{entityKey}/{instanceId / disk / path / entityKey.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 9.22.0.
Workaround: applications should restrict `downloads.
Search webserver/proxy logs for unusual GET /sharp/{globalFilter}/download/{entityKey}/{instanceId requests with malformed payloads or SQL meta-characters. Run grep -r 'code16/sharp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'code16/sharp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
code16/sharpを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /sharp/{globalFilter}/download/{entityKey}/{instanceId' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /sharp/{globalFilter}/download/{entityKey}/{instanceIdへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply temporary workaround mitigate
applications should restrict `downloads.パッチが適用されるまでの応急処置として、applications should restrict `downloads. を実施。回避策の副作用 (機能低下) を確認した上で。
-
4Apply patch patch
Upgrade code16/sharp to 9.22.0ステージング環境で 9.22.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
5Post-deployment verification verify
Replay attack against GET /sharp/{globalFilter}/download/{entityKey}/{instanceId on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com