Vulnerability in cyborg (DEBIAN-CVE-2026-40214)

Summary

Vulnerability in cyborg (DEBIAN-CVE-2026-40214). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 14.0.0-3+deb13u1 or later.

Original description

The description as published by the source.

In OpenStack Cyborg before 16.0.1, the Accelerator Request (ARQ) API does not enforce project ownership at any layer. The project_id column in the database is never populated (NULL for every ARQ), database queries have no project filtering, and policy checks are self-referential (the authorize_wsgi decorator compares the caller's project_id with itself rather than the target resource). Any authenticated non-admin user can complete various actions such as deleting ARQs bound to other projects' instances, aka cross-tenant denial of service.

Source: OSV.dev (Open Source Vulnerabilities) OSV

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 DEBIAN-CVE-2026-40214 has been found in cyborg.
Risk of unauthorized operations or information disclosure.
What to do: upgrade cyborg to 14.0.0-3+deb13u1 or later.
If unsure, ask your IT team or search "cyborg DEBIAN-CVE-2026-40214" on the vendor's site.

DEBIAN-CVE-2026-40214 (cyborg)
Attack vector: remote (network-reachable) / no user interaction
Patched: 14.0.0-3+deb13u1 — 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.

❓ What is the problem

A vulnerability (unclassified) exists in cyborg.

📍 Affected scope

Check the vendor advisory for the affected versions of cyborg.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 14.0.0-3+deb13u1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'cyborg' . 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

1
Identify exposure identify
```
grep -r 'cyborg' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で cyborg を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade cyborg to 14.0.0-3+deb13u1
```
ステージング環境で 14.0.0-3+deb13u1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:13 cyborg

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.0.0-3+deb13u1"}]}]

Debian:14 cyborg

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.0.0+git+2026.04.26.b8edfa06f1-1"}]}]

References

advisory security-tracker.debian.org