Path Traversal in /api/app-icons/[filename] (CVE-2026-42564)
Summary
Path traversal in /api/app-icons/[filename] (CVE-2026-42564). Confidential information can be exposed externally. Mitigation: upgrade to 1.22.0 or later.
Original description
The description as published by the source.
jotty·page is a self-hosted app for your checklists and notes. Prior to 1.22.0, an unauthenticated path traversal vulnerability exists in /api/app-icons/[filename]. The filename route parameter is joined into a filesystem path without traversal/boundary validation, allowing file reads outside data/uploads/app-icons/. This vulnerability is fixed in 1.22.0.
Source: NIST National Vulnerability Database 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-42564 has been found in /api/app-icons/[filename].
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: upgrade /api/app-icons/[filename] to 1.22.0 or later.
If unsure, ask your IT team or search "/api/app-icons/[filename] CVE-2026-42564" on the vendor's site.
CVE-2026-42564 (/api/app-icons/[filename]) — CWE-22 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.22.0 — apply immediately
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.
Path traversal (CWE-22) exists in /api/app-icons/[filename].
Check the vendor advisory for the affected versions of /api/app-icons/[filename].
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally.
Update to 1.22.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで /api/app-icons/[filename] を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade /api/app-icons/[filename] to 1.22.0ステージング環境で 1.22.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov