Vulnerability in OpenProject (CVE-2026-67527)
Summary
Vulnerability in OpenProject (CVE-2026-67527). Data can be tampered with by attackers. Exploitable via PATCH /api/v3/work_packages/{id}. Mitigation: upgrade to 17.6.0 or later.
Original description
The description as published by the source.
OpenProject is open-source, web-based project management software. Prior to 17.6.0, PATCH /api/v3/work_packages/{id} accepted _links.fileLinks and allowed authenticated users with edit_work_packages but without manage_file_links to resolve Storages::FileLink records by raw id, detach or hard-delete existing FileLinks, and re-parent FileLinks from other projects to an attacker-controlled work package, exposing origin filename, origin id, and MIME type metadata. This issue is fixed in 17.6.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-67527 has been found in OpenProject.
Attackers can target a specific entry point like PATCH /api/v3/work_packages/{id} over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.6/10.
What to do: upgrade OpenProject to 17.6.0 or later.
If unsure, ask your IT team or search "OpenProject CVE-2026-67527" on the vendor's site.
CVE-2026-67527 (OpenProject) — CWE-862 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /api/v3/work_packages/{id}
Patched: 17.6.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-862) exists in OpenProject. Attackers reach the vulnerable code path via PATCH /api/v3/work_packages/{id}.
Check the vendor advisory for the affected versions of OpenProject. Attack surface: PATCH /api/v3/work_packages/{id}.
Severity: High (CVSS 7.6/10). Data can be tampered with by attackers.
Update to 17.6.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 PATCH /api/v3/work_packages/{id} requests with malformed payloads or SQL meta-characters. Run grep -r 'OpenProject' . 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 'OpenProject' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
OpenProjectを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'PATCH /api/v3/work_packages/{id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PATCH /api/v3/work_packages/{id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade OpenProject to 17.6.0ステージング環境で 17.6.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against PATCH /api/v3/work_packages/{id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- web github.com