Vulnerability in Dockyard (CVE-2026-39848)
Summary
Vulnerability in Dockyard (CVE-2026-39848). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.1.0 or later.
Original description
The description as published by the source.
Dockyard is a Docker container management app. Prior to 1.1.0, Docker container start and stop operations are performed through GET requests without CSRF protection. A remote attacker can cause a logged-in administrator's browser to request /apps/action.php?action=stop&name= or /apps/action.php?action=start&name=, which starts or stops the target container. This vulnerability is fixed in 1.1.0.
Source: NIST National Vulnerability Database NVD
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-39848 has been found in Dockyard.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade Dockyard to 1.1.0 or later.
If unsure, ask your IT team or search "Dockyard CVE-2026-39848" on the vendor's site.
CVE-2026-39848 (Dockyard) — CWE-306 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.1.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.
A vulnerability (CWE-306) exists in Dockyard.
Check the vendor advisory for the affected versions of Dockyard.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.1.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. Run grep -r 'Dockyard' . 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 'Dockyard' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Dockyardを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Dockyard to 1.1.0ステージング環境で 1.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com