Vulnerability in LinkAce (CVE-2026-45344)
Summary
Vulnerability in LinkAce (CVE-2026-45344). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.5.6 or later.
Original description
The description as published by the source.
LinkAce is a self-hosted archive to collect website links. Prior to 2.5.6, the setup database configuration flow on uninitialized LinkAce instances accepts attacker-controlled database credential fields and writes them back into .env without escaping. A remote attacker who can reach the setup endpoints and supply a database they control can inject mail configuration variables and achieve command execution when the application later sends mail. This vulnerability is fixed in 2.5.6.
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-45344 has been found in LinkAce.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade LinkAce to 2.5.6 or later.
If unsure, ask your IT team or search "LinkAce CVE-2026-45344" on the vendor's site.
CVE-2026-45344 (LinkAce) — CWE-74 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.5.6 — 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-74) exists in LinkAce.
Check the vendor advisory for the affected versions of LinkAce.
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover.
Update to 2.5.6.
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 'LinkAce' . 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 'LinkAce' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
LinkAceを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade LinkAce to 2.5.6ステージング環境で 2.5.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov